Fix: Flux Sync status and action are off when namespace is unrelated to flux resource path

What does this MR do and why?

In case the Flux resource namespace is different from the environment namespace (which could happen when the user created an environment from the API), the Flux resource sync status badge gets into the "Refresh needed" state. This is caused by the k8sConnectionStatusQuery receiving the namespace of the environment instead of the specific FLux resource namespace.

The KubernetesStatusBar component now receives the fluxNamespace prop, which specifies the namespace of the Flux resource being displayed. This allows the component to display the correct status information for the specified namespace.

MR acceptance checklist

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

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

1. Follow this guide to start with the Flux.

2. Visit Project -> Operate -> Environments

3. Create/Edit an environment using the UI

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:

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

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

9. Select a namespace that is different from your Flux resource namespace.

10. Set Flux resource via API

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

Related to #498083 (closed)