Implement flux status refresh for Kubernetes Resources on the Environments Page
Description
This is the follow-up for !146761 (comment 1803960754) from @anna_vovchenko.
With the re-subscription for k8s resources implemented, we're missing the re-subscription for the flux resource status, as they the watcher there has the simmilar issue, as the one for resources.
Implementation proposal
Since the refresh functionality is something that any k8s related resource could be using, it makes sense to consider a refactoring that would unify existing k8s related graphql queries. Currently we have similar implementations for k8s resolvers for kubernetes_dashboard
and environment/kubernetes
I suggest to unify the implementations into a single k8s resources graphql resolver. This way we can easier share watcher functionality between all the graphql resource queries.
For triggering the mutation, we could update reconnectToCluster
mutation to accept an array of resources to resubscribe to. This way the clients can be flexible about what resources they want to resubscribe to.