✨ Allow a user to provide a custom metric provider for firing metrics

[jonathan-innis]

Fixes #3094

This change updates controller-runtime to expose MetricProviders for all of the subsystems where we expose metrics. This allows other controllers that leverage controller-runtime to do things like forward metrics to EMF (Embedded Metrics Format on AWS) rather than exposing them through Prometheus

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jonathan-innis
Once this PR has been reviewed and has the lgtm label, please assign fillzpp for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jonathan-innis]

/test all

[jonathan-innis]

/test all

[jonathan-innis]

/test all

[alvaroaleman]

I think rather than introducing the complexity of making this configurable its preferred to instead add the controller-runtime metrics registry to your own, here is an example of doing it with otel: #305 (comment)

/hold