[internal/patch/logr] Add funcr package

[mx-psi]

What does this PR do?

Add funcr patch module to use the funcr package in logr v0.4.0. See https://github.com/DataDog/datadog-agent/blob/main/internal/patch/logr/funcr/README.md for further details.

Motivation

Be able to bump the OpenTelemetry Collector.

Additional Notes

This is terribly hacky and it only works because a logr.Logger was an interface on v0.4.0 but.. it works:

• The behavior should be the same as with logger v1.2.2 because we are just using the v1.2.2 logger under the hood
• If something fails it will fail to compile, not fail at runtime
• Whenever we don't need this we will get an 'ambiguous import' error which can be fixed.

Possible Drawbacks / Trade-offs

Maybe there is some difference in behavior that I am not aware of that makes this package malfunction. I think this is unlikely, but the possibility is there.

Describe how to test/QA your changes

To be tested as part of the Collector bump.

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• The appropriate team/.. label has been applied, if known.
• Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the config template has been updated.

[KSerrania]

LGTM but it's sad that we have to resort to this 😢

[mx-psi]

LGTM but it's sad that we have to resort to this 😢

Yes :( If everything goes well and kubernetes/kubernetes#106536 gets fixed, we could potentially remove this in April or August, depending on the Kubernetes release.