Add statefulStates page to the Kubernetes dashboard

What does this MR do and why?

This MR adds the statefulSets page to the Kubernetes dashboard. It uses the same components and designs as the pods page. This MR adds the query, resolver, and the new path. This MR is very similar to !138685 (merged), which introduced the deployments page.

Screenshots or screen recordings

How to set up and validate locally

1. Enable the k8s_dashboard feature flag

      Feature.enable(:k8s_dashboard)

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

2. 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.

3. 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>

4. 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 Deploy the GitLab Agent (agentk) with k3d section to create a local cluster and connect your agent with the cluster.

5. Navigate to https://gdk.test:3443/-/kubernetes/<yout-agent-id>/statefulsets

6. Verify the page, it's data and the drawer appearing on the table row click.

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 #428314 (closed)