Fix kubelet cri round trip test

[liggitt]

What type of PR is this?

/kind bug
/kind test

What this PR does / why we need it:

Fixes the kubelet cri memory-compatibility test to recurse properly

Found while working on a similar test for #107970

The test wasn't recursing into slices correctly (it was grabbing the type of each slice's element, then the type of the type (which is a reflect type), then asserting those were equal, which of course they were.

Once we started recursing correctly, two differences got flagged:

• enum content of the protobuf struct tags, which is not relevant to the wire serialization and is expected to be difference since it refers to a package-qualified type
• several unhandled type declarations that were aliases of int32... this adds handling for that case and asserts both sides are int32.

/cc @saschagrunert
/sig node

NONE

[k8s-ci-robot]

@liggitt: The label(s) kind/test cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?

/kind bug
/kind test

What this PR does / why we need it:

Fixes the kubelet cri memory-compatibility test to recurse properly

Found while working on a similar test for #107970

The test wasn't recursing into slices correctly (it was grabbing the type of each slice's element, then the type of the type (which is a reflect type), then asserting those were equal, which of course they were.

Once we started recursing correctly, two differences got flagged:

• enum content of the protobuf struct tags, which is not relevant to the wire serialization and is expected to be difference since it refers to a package-qualified type
• several unhandled type declarations that were aliases of int32... this adds handling for that case and asserts both sides are int32.

/cc @saschagrunert
/sig node

NONE

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/test-infra repository.

[saschagrunert]

Thanks!
/lgtm
/cc @ehashman

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, saschagrunert

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/cri/remote/OWNERS [liggitt]

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

[saschagrunert]

/triage accepted
/priority important-soon

[saschagrunert]

/test pull-kubernetes-e2e-kind-ipv6