Query Organization cluster agents when attempting to create workspace

Issues:

Frontend: Query organization cluster agents on ... (#534676 - closed)

Rename remoteDevelopmentClusterAgents type inte... (#536263 - closed)

What does this MR do and why?

This MR includes support for querying organization cluster agents when creating a workspace. It also cleans up the deprecated remoteDevelopmentClusterAgents in favour of workspacesClusterAgents in GraphQL APIs used in the frontend.

References

Frontend: Query organization cluster agents on ... (#534676 - closed)

Rename remoteDevelopmentClusterAgents type inte... (#536263 - closed)

Screenshots or screen recordings

In this recording, I enable an agent for the organization, allowing the flightJs project access to it when creating a workspace.

Screen_Recording_2025-06-16_at_8.40.34_AM

How to set up and validate locally

• Setup Workspaces locally
• Make a project you would want to create a workspace for, but make sure it does NOT share a group with the cluster Agent you created in the steps above.
• Enable the workspaces_agents_availability_admin feature flag
• In the "Available agents for workspace" settings section in the admin UI, enable the agent you configured in step 1
• On attempting to create a workspace for your project, you see the agent you enabled as an option, and you successfully use it to create a workspace
• Likewise, disabling it in the admin UI makes it unavailable for workspace creation

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.