Render Kubernetes resources in Environment index page

What does this MR do and why?

This MR adds a logic of retrieving the associated agent information when the user selects an environment on the environment page. It also refactors the kuberenetes_agent_info component to not duplicate the graphql query.

Screenshots or screen recordings

The agent is selected from the environment settings page:

The Kubernetes overview section appears for the environment that has an associated agent:

Here's a recording of the full flow: internal link

How to set up and validate locally

1. Enable the environment_settings_to_graphql feature flag

         Feature.enable(:environment_settings_to_graphql)

2. Visit the Environments page:

   • Project -> Operate -> Environments if the new navigation is enabled
   • Project -> Deployments -> Environments if the new navigation is not enabled

3. Create/Edit an environment using the UI

4. To create an agent that can appear in the agent selector:

   1. Enable kas_user_access feature flag

      Feature.enable(:kas_user_access)

   2. Enable expose_authorized_cluster_agents feature flag

      Feature.enable(:expose_authorized_cluster_agents)

   3. Enable kas_user_access_project feature flag

      Feature.enable(:kas_user_access_project, Project.find(<your-project-id>))

   4. Enable KAS on your GDK (steps 1-2 from the guide).

   5. Visit the Project -> Infrastructure -> Kubernetes clusters page and create an agent following the instruction from the modal.

      • Select the "Connect a cluster" button
      • The modal should pop up
      • In the modal select "Select an agent or enter a name to create new"
      • You probably won't have any configured agents to show up in the list, create a new one by typing the name of your choice
      • The button should appear at the bottom of the list saying "Create agent: <your-agent-name>"
      • Select the button and click "Register" in the next view.
      • Save the token to use it in the next point.

   6. Add the following configuration inside your project in .gitlab/agents/<your-agent-name>/config.yaml for the user_access agent:

      gitops:
        manifest_projects:
        - id: <your-group>/<your-project>
      user_access:
        access_as: 
          agent: {}
        projects:
        - id: <your-group>/<your-project-to-share-agent-with>

   7. Note that the shared agents should be connected to the cluster in order to appear in the list. Please follow points 3-8 from the guide and then the (Optional) Deploy the GitLab Agent (agentk) with k3d section to create a local cluster and connect your agent with the cluster.

5. Select an agent from the dropdown in the Environments settings page and save the change.

6. Visit the Environments page and select the environment that has an associated agent.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #390769 (closed)