Fusion Fleet/Realm management cmdlets (realm-connections, topology-groups, remote-realms)

[juemerson-at-purestorage]

Fleet/realm object management — building and managing the fleet (2.25–2.27). Partially seeded (Get-PfbFleet, Get-PfbRealm exist). Roadmap priority P2-7.

Distinct from #25 (Fusion context_names injection): #25 owns the context-execution plumbing (running a cmdlet against a chosen array); this issue is the object-management cmdlets. These cmdlets will inherit the centralized context mechanism from #25 at runtime but are not blocked by it.

• realm-connections GET/POST/DELETE (+ /connection-key GET/POST/DELETE)
• remote-realms GET
• topology-groups GET/POST/PATCH/DELETE (+ /arrays GET, /members GET/POST/DELETE)
• remote-arrays PATCH
• storage-classes/members GET
• fleets/members/batch POST (may fold into the batch-ops issue)

⚠ The same management-access-policies 403 lab blocker may affect fleet testing — confirm a test path.

Blocked on: nothing.
Owner: TBD.

[juemerson-at-purestorage]

Bug found while live-testing fleet setup: New-PfbFleetMember doesn't match the actual REST wire contract.

Per the FlashBlade REST API spec, POST /fleets/members must be called from the array that is joining the fleet, with a JSON body:

{
  "members": [
    { "key": "<fleet key from New-PfbFleetKey>", "member": { "id": "<this array's own id>" } }
  ]
}

plus fleet_names (or fleet_ids) as a query parameter identifying the target fleet.

The current implementation instead sends fleet_names and member_names as bare query parameters with no request body at all — no fleet key, no self-identification of the joining array. As implemented, this cmdlet can never have worked against a real array; it has no way to satisfy the fleet-key requirement.

Confirmed live against a real 3-array Fusion test fleet — the shape above succeeds; the cmdlet's current shape does not.

Given the pipelining-to-Set-PfbContext ideas already floated on PR #22, holding off on fixing this until the Fusion context design lands, since the final parameter shape here may end up driven by that work rather than being a standalone fix.