Test saved camera profiles from the Cameras page

[elkampu]

Goal

Let users verify a stored camera profile without creating a capture session or exposing its password in the page.

Acceptance criteria

• Each camera card has a Test connection action that posts only its profile ID to the existing /api/camera/test endpoint.
• While pending, disable only the selected card's action and expose its busy state. Restore it in a finally path.
• Put an accessible success or failure message beside that card in a role="status", aria-live="polite" region, including request duration when available.
• The stored password is never rendered into HTML, JavaScript, a query string, a request body, or a diagnostic.
• The action works for the demo profile and real saved profiles and can be retried after an error.
• Existing antiforgery handling is reused.
• A page/integration test stores a profile with a sentinel password and proves the password is absent from the Cameras response HTML.
• Tests cover demo and saved-profile success, camera failure, and retry; the request body contains only profileId.
• Tests and formatting checks pass.

Please comment with your proposed approach before starting. A draft PR is welcome.

[iibaranov-IG]

Proposed approach:

• render one Test connection control and adjacent polite live-status region per saved camera card
• send only the profile ID as JSON to the existing antiforgery-protected endpoint
• keep pending state scoped to the selected card and restore it in finally so failures remain retryable
• reuse the existing connection result shape, including duration when supplied
• add page/integration coverage proving a sentinel stored password never appears in the Cameras HTML, plus browser-facing JavaScript unit coverage for success, failure, retry, and request shape
• run the complete test and formatting suites

No camera credentials will be rendered or copied into client state.