Update to `controller-runtime v0.XX.0` and adapt to native client.Apply

[c-pius]

Description

Bump controller-runtime to v.0.XX.0 and migrate to the native client.Apply accordingly. For template-operator, this was done here: kyma-project/template-operator#398 Also note that for SubResourceWriter, it is not supported yet: #2706

The challenge we have in lifecycle-manager is that we have our own ProxyClient which must now implement the Apply method accordingly. To match the signature, we need to pass the object as machineryruntime.ApplyConfiguration, but it is not obvious how to get the GVK from that object to get the resource mapping. This needs to be thought through thoroughly.

Reasons

v0.22.0 of controller-runtime deprecated client.Apply in favor of "Native SSA Support" via client.Client.Apply. We need to adapt accordingly.

Acceptance Criteria

• in KLM and template-operator
  • updated to controller-runtime v0.XX.0
  • fixed the ClientProxy
  • replaced deprecated client.Apply usage with client.Client.Apply
  • created lint exceptions for usages with SubResources and linked occurrences to ticket Replace SubResourceWriter.Patch with native apply #2706

Feature Testing

No response

Testing approach

No response

Attachments

No response

[c-pius]

We agreed to skip this version as proposed by @lindnerby. Let's wait for native SSA support to further mature in the next version of controller-runtime before updating.

In case a CVE should pop up for cr 0.21.0, we can update to 0.22.0 but without adapting to the new client.Client.Apply.

[c-pius]

FYI: deprecation was reverted: kubernetes-sigs/controller-runtime#3307