Update Flux dependencies

[yiannistri]

Closes #3810

What changed?
Updated Flux dependencies.

Why was this change made?
To keep up with Flux changes.

How was this change implemented?
Updated the go modules for the Flux v1 APIs. Also updated code to accommodate controller-runtime version bump.

How did you validate the change?
Run locally

Release notes
N/A

Documentation Changes
N/A

[chanwit]

The codes around gvks look good to me.

We need to revisit this, the resulting change is causing applications and sources to appear twice

[yitsushi]

I don't think we can fix the apiVersion under the YAML tab on the resource details page. 😞

Summary:
go-client does not care about GroupVersion only the Kind. On Get and List, the requested object's gvk will be set to be the same as the request was.

If we request v1beta2 we will get a v1beta2, if we request a v1 we will get a v1 with the same object. If we iterate over all known group versions, we will get a response on all of them with the same objects. If we request only v1 (as it does not matter) it will show v1 even if the object is v1beta2.

My assumption on the reason:
You can't have multiple resources with the same Kind, Namespace, and Name, does not matter the apiVersion.

---

I went down to a deep rabbit hole with controller-runtime and stopped when I was in the source code of client-go about handling metadata lists. My assumption (and it matches with our experiences) is, the list query does not care about group versions at all.

For example controller-runtime sets the object's gvk to the requested gvk on list.
It does the same for get.

[chanwit]

In that case, we would

1. look for the latest version
2. use it to set a GVK
3. document that Weave GitOps will display object with the latest version of schema in the YAML tab.

wdyt?

[yitsushi]

document that Weave GitOps will display object with the latest version of schema in the YAML tab.

my only issue with that, it can be misleading, not because "oh that line is different", but given version may not have a specific field, or it has a different type. The UI is presented mostly to people without kubectl access (I think) because they don't have for security reasons, or the cluster is behind a firewall and only the UI is exposed on a private network address. Yes there is a command above the yaml output, but if someone checks the resources and they try to understand something with the docs open in another tab, they can be confused.