Cluster node recovery test, set kind node image for all nodes.

[alex-hunt-materialize]

Explicitly set the node image for all kind nodes in the cluster node recovery tests.

Motivation

• This PR fixes a previously unreported bug.
  If not specified, kind will choose the latest node image supported by that kind version. This is a moving target if developers have different versions of kind, and can just fail if we set the node image for some nodes but not others. If the version set for some nodes is old, the auto-selected version for the nodes not set may be more than one minor version newer than the one that was explicitly set, which is not supported by kubeadm (the kubeadm version is chosen by kind to be the version of the highest node version in the cluster).

This is a follow up to #32710 which should prevent this failure in the future (we'll still want to upgrade nodes from time to time, though).

Tips for reviewer

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.