chore: add function to group entries by action in changeset output

[94DanielBrown]

This can then be used to improve cardinality of logs in kustomize-controller.
I have tested and will make a PR to kustomize-controller which does this:

log.Info("server-side apply for cluster definitions completed", "output", changeSet.ToMap())
+                       log.Info("server-side apply for cluster definitions completed", "output", changeSet.ToGroupedMap()

It helps with fluxcd/flux2#4036

[stefanprodan]

We can't just change the log format of a GA controller, we'll break the filters people have for these logs just to comply with a small subset that are using elastic. If we decide to get this in, it needs to be under a feature flag in kustomize-controller.

[94DanielBrown]

Yeah that makes sense

But is there any harm getting the function added into here for now and then I can look at adding the feature flag in the controller and using it there after, if you agree that's an okay thing to do?

[stefanprodan]

We need to analyse all the logging across all controllers and check if the structure logs contain keys with namespace/name/kind/etc. Changing this one log line may not solve the issue with ES.

[94DanielBrown]

Can it not just be added as a feature flag for just the kustomize controller as this is where the issue are?

Also if it's added here as a function it doesn't have to be used but it makes it easier to use if someone want to run a fork of the controller to sort out the logging in ES/OS ?

[stefanprodan]

Can it not just be added as a feature flag for just the kustomize controller as this is where the issue are?

Yes, what I'm saying is that there may be other places where the log keys are high cardinality, and the feature flag should fix this everywhere. I'll run some queries on my clusters and see if such logs are in other places besides here.