Support for Multiple AMT Connection (CIRA) Handling

[graikhel-intel]

Description of Request

Implement the necessary wiring in Console to handle multiple simultaneous AMT device connections, each identified by its AMT GUID, and make sure every API call is routed to the correct active CIRA channel for that specific device.

This should allow Console to correctly manage and route communication when multiple AMT devices are connected at the same time.

Dependencies

• Implement Secrets Management and Provisioning Flows in Console + RPC-Go to support cloud deployment Implement Secrets Management and Provisioning Flows in Console + RPC-Go to Support Cloud Deployment #597
• Add Support for CIRA in Console Add Support for CIRA #665

Scope

• Console can handle multiple concurrent AMT device connections through CIRA, identified by AMT GUID.
• Each API request is routed to the correct CIRA channel for the target device.
• Maintain accurate tracking for each connection, including ID, status, and last active time.
• Handle disconnected or reconnected devices gracefully.
• Validate multi-device operations such as KVM, Power, SOL/IDER, and provisioning.
• Add logs and metrics showing active connections and routing behavior.
• Include basic test coverage (unit, integration, and end-to-end) to ensure routing stability and correctness.

Open Questions / Needs Brainstorming

MPS-Router integration details

What’s the integration plan with MPS-Router (which routes API requests to the correct MPS when multiple MPS instances exist)?

Reuse or new component? Decide whether to: Reuse and extend the existing MPS-Router, or Create a new routing component?

K8s / Deployment notes

• Update our K8s recipes and AKS/EKS docs for Console