Fix cpu resource metric type by changing to counter

[dashpole]

What type of PR is this?
/kind bug

What this PR does / why we need it:
CPU metrics should be counters, not gauges. When I initially created the kubelet resource metrics endpoint in #73946, I mistakenly made CPU metrics a gauge. When this was refactored to make use of the metrics stability framework in #86282, the cpu metrics were renamed to omit the _total suffix, which caught the attention of some sig instrumentation members.

Since the endpoint was newly added in 1.18, we have decided to just fix the metric without a deprecation period, and cherry-pick the fix back to the 1.18 release.

Does this PR introduce a user-facing change?:

In the kubelet resource metrics endpoint at /metrics/resource, change the names of the following metrics:
- node_cpu_usage_seconds --> node_cpu_usage_seconds_total
- container_cpu_usage_seconds --> container_cpu_usage_seconds_total
This is a partial revert of #86282, which was added in 1.18.0, and initially removed the _total suffix

/assign @brancz @logicalhan @serathius @ehashman
/hold
to make sure we are all in agreement about this change
cc @kubernetes/sig-instrumentation-bugs

[dashpole]

/priority critical-urgent

[logicalhan]

/lgtm

[serathius]

/lgtm
cc @x13n

[ehashman]

👍

[RainbowMango]

I'm the guys who omitted the _total suffix because as per promlint non-counter metrics should not have "_total" suffix.
Sorry about that. And please @brancz confirm about this change.
/lgtm

[brancz]

/lgtm
/approve

I think we are now in consensus @dashpole, I think you can now feel free to remove the hold label.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brancz, dashpole

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:

• pkg/kubelet/metrics/OWNERS [dashpole]

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

[RainbowMango]

/hold cancel
We are all on the same page now.

[ehashman]

/test pull-kubernetes-e2e-gce

[dashpole]

/test pull-kubernetes-e2e-gce

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.