Switch Gitopssets UI to use OSS endpoints for querying/suspend/sync

[foot]

What changed?

Remove all the dedicated gitopssets endpoints:

• GET /v1/gitopssets
• GET /v1/namespaces/{namespace}/gitopssets/{name}
• GET /v1/namespaces/{namespace}/gitopssets/{name}/inventory
• PATCH /v1/namespaces/{namespace}/gitopssets/{name}/suspend
• PATCH /v1/namespaces/{namespace}/gitopssets/{name}/sync

Add GitOpsSet as a supported kind to OSS's query system endpoints

Use OSS equivalent endpoints instead.

Behaviour changes?

Yes!

• We don't try and report the health of confimaps anymore etc as "⚠️ unknown" as we delegate to the health checker system.
• The OSS querier that we are now using for listing gitopssets in the table view works slightly differently to the non-explorer EE querier. You will only see GitOpsSets in namespaces that you have permissions to read the classic list of flux resources as well. This may cause issues in some tenancy setups.
  • Workaround: enable the explorer

Why was this change made?

API Cleanup

How was this change implemented?

Removing all the gitopssets endpoints and mopped up the UI

How did you validate the change?

• Explain how a reviewer can verify the change themselves

• tilt up

• Test gitopssets sync / suspend / graph / events / yaml etc

• Edit tools/dev-values.yaml and disable the explorer and check that gitopssets listing table still works

Release notes

Documentation Changes

Other follow ups

[foot]

Workaround: enable the explorer

Perhaps we could actually enable the explorer + gitopssets for the next release by default, wdyt @enekofb ?

[enekofb]

Workaround: enable the explorer

Perhaps we could actually enable the explorer + gitopssets for the next release by default, wdyt @enekofb ?

Go go go 🚀

[AlinaGoaga]

Working great! 🥳