chore: Reduce code duplication for metadata metric families

[mrueg]

What this PR does / why we need it:
There are common metrics shared among all resources for creation, deletion, labels and annotations. We can deduplicate code this way and currently I implemented it for pods (I will apply it to other resources as well).

The downside with the current approach is, that we can flip stability only on and off for all of them, which I think is fine because of the common nature of these metrics.

How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
None
Which issue(s) this PR fixes: (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged)
Fixes #

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrueg

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mrueg]

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

[CatherineF-dev]

qq: why does it have 4 new metrics while the above only deletes 2 metrics (annotation and labels)?

Seems tests are passing, just want to see what happened.

[mrueg]

I moved the _created _labels _annotations _deleted metrics into the metadata file. This is still WIP, hoping to reduce code duplication. I ran into some issues with the csr resource which relies on info outside of the metadata scope.

[CatherineF-dev]

/triage accepted