Add monitored_components to outage schemas

[Copilot]

Ports the monitored_components field introduced in PowerSystems.jl#1672 to the JSON Schema definitions for outage supplemental attributes.

Changes

• Operations/SupplementalAttributes/FixedForcedOutage.json, GeometricDistributionForcedOutage.json, PlannedOutage.json: add optional monitored_components property — an array of UUID-formatted strings with uniqueItems: true and default []. Not added to required since the upstream constructors default to an empty set.

Schema fragment

"monitored_components": {
  "type": "array",
  "items": { "type": "string", "format": "uuid" },
  "uniqueItems": true,
  "default": [],
  "description": "UUIDs of devices whose post-contingency state should be modeled when this outage occurs. Empty by default; semantics of an empty list are decided by the downstream consumer."
}

The Set{Base.UUID} upstream type is represented here as a UUID string array with uniqueItems: true. Empty-set semantics ("monitor nothing" vs. "monitor everything") are intentionally left to the downstream consumer, matching the upstream contract.

[jd-lara]

@josephmckinsey do we need to move the vector to ids instead of UUIDs?

[josephmckinsey]

@josephmckinsey do we need to move the vector to ids instead of UUIDs?

Yes.