[receiver/kubeletstats] Excessive float64 precision in CPU scraper utilization metrics

[ChrsMark]

Component(s)

No response

Describe the issue you're reporting

Similarly to #46177 we need to consider about following what hostmetrics receiver introduced regarding the precision in CPU utilisation metrics.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[github-actions]

Pinging code owners for receiver/kubeletstats: @dmitryax @TylerHelmuth @ChrsMark. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triage' to set the priority and remove the needs-triage label.

[github-actions]

Pinging code owners:

• receiver/kubeletstats: @dmitryax @TylerHelmuth @ChrsMark

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