memorymanager: fix checkpoint file comparison

[Tal-or]

What type of PR is this?

/kind bug

What this PR does / why we need it:

For a resource within a group, such as memory,
we should validate the total Free and total Reserved size of the expected machineState and state restored from checkpoint file after kubelet start.
If total Free and total Reserved are equal, the restored state is valid.

The old comparison however was done by reflection.

There're times when the memory accounting is equals
but the allocations across the NUMA nodes are varies.

In such cases we still need to consider the states as equals.

Which issue(s) this PR fixes:

Fixes ##113130

Special notes for your reviewer:

This PR use as a replacement for #114501 which is not active for a long time now and is needed for MemoryManager GA graduation.
see: kubernetes/enhancements#1769 (comment)

Does this PR introduce a user-facing change?

NONE

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

- [KEP]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1769-memory-manager#design-overview

[k8s-ci-robot]

Hi @Tal-or. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[Tal-or]

/cc @ffromani @bart0sh

[ffromani]

/ok-to-test
/priority important-longterm
/triage accepted

[bart0sh]

/retest

[ffromani]

provisional LGTM (need to do another pass).
The ordering of allocation should not matter indeed, only the totals should matter

[ffromani]

provisional LGTM

since we cannot guarantee we recreate pods in the very same ordering across restarts, there are multiple legal representations (even including pinning) of the same memory state, thus we should check the aggregate values

[ffromani]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b5f370a652a9e22d8f83920885c9f39569958492

[ffromani]

/test pull-kubernetes-node-kubelet-serial-containerd
/test pull-kubernetes-node-kubelet-serial-containerd-sidecar-containers
/test pull-kubernetes-node-kubelet-serial-cpu-manager
/test pull-kubernetes-node-kubelet-serial-hugepages
/test pull-kubernetes-node-kubelet-serial-memory-manager
/test pull-kubernetes-node-kubelet-serial-topology-manager

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrunalp, Tal-or

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/cm/OWNERS [mrunalp]

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