[k8sclusterreceiver] Some metric units don't follow Otel semantic conventions

[bertysentry]

Describe the bug
Some metrics don't follow Otel semantic conventions

Steps to reproduce
Nothing to reproduce. The problem lies in the specification of the receiver itself.

What did you expect to see?
Metrics that count objects should use units with brackets {} and not 1

Example:

• k8s.container.restarts ==> Unit: "{restarts}"
• k8s.cronjob.active_jobs ==> Unit: "{jobs}"
• k8s.job.active_pods ==> Unit: "{pods}"
• etc.

What did you see instead?
Many metrics specify unit 1 to report a count of objects:

• k8s.container.restarts
• k8s.cronjob.active_jobs
• k8s.job.active_pods
• etc.

Unit 1 must be used only for fractions and ratios.

What version did you use?
Main branch

What config did you use?
N/A

Environment
N/A

Additional context
N/A

[github-actions]

Pinging code owners: @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/k8scluster: @dmitryax

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.