[KEP-2400] Add a container_swap_limit_bytes metric

[iholder101]

What type of PR is this?

/kind feature
/sig node

What this PR does / why we need it:

Swap metrics were originally added as part of #118865.

This PR adds a container_swap_limit_bytes to report the calculated swap limit for each container and be available at the /metrics/resource endpoint.

After this is merged, we can consider adding this as part of kubectl top pod/node --show-swap, as a follow-up to #129458.

This is NOT a blocker for KEP-2400 GA, but rather a nice-to-have addition.

Which issue(s) this PR is related to:

Fixes #132228

Does this PR introduce a user-facing change?

Adds a `container_swap_limit_bytes` metric to expose the swap limit assigned to containers under the `LimitedSwap` swap behavior.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2400-node-swap/README.md

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[iholder101]

/cc @ajaysundark @haircommander @yuanwang04

[k8s-ci-robot]

@iholder101: GitHub didn't allow me to request PR reviews from the following users: yuanwang04.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @ajaysundark @haircommander @yuanwang04

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[iholder101]

/test pull-kubernetes-unit-windows-master

[haircommander]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 778e43f05c4e5a310aaa4ee00ef1167f9d325f15

[iholder101]

@mrunalp (for e2e node tests)
@dashpole (for metrics)

can you please take a look for approval?

This PR was LGTMed twice above. The LGTM was dropped due to a rebase.
@mrunalp @dashpole do you mind having a look for approval?

[ajaysundark]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 6f4f3370680c7d9c1525f6e014db016a79e0ede1

[ajaysundark]

/retest

[iholder101]

Hey @dashpole!
This PR was LGTMed from the node side by 4 people [1][2][3][4].

Is there something missing from your side?
Thanks!

[1] #132348 (comment)
[2] #132348 (comment)
[3] #132348 (comment)
[4] #132348 (comment)

[dashpole]

/lgtm
for sig-instrumentation

[iholder101]

@SergeyKanzhelev would you be willing to approve this? Thanks!

[dchen1107]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ajaysundark, dashpole, dchen1107, iholder101

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,dchen1107]
• test/e2e_node/OWNERS [dchen1107]

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