Update API endpoint for Flux resource
Proposal
Currently, we use the v1beta1 endpoint instead of the recommended v1 endpoint for fetching the Flux resource status.
Since v1beta1 has already been deprecated and is scheduled for removal in Q3, it's crucial to transition to the v1 APIs promptly. This update ensures compliance with standards and potentially improves system performance.
The new API endpoint also returns the detailed status field including inventory entries, which is critical for building the tree view.
As the API endpoint is stored in the database once the user selects the FLux resource, we'll need to update it on the fly on the frontend.