compatibility-versions: Migrate prow jobs to use precompiled binaries

[aaron-prindle]

Currently ci-kubernetes-e2e-kind-compatibility-versions builds binaries before testing but the test would be faster and use less compute if it instead used precompiled binaries. Related comment here:
#33591 (comment)

slightly more work but cheaper/faster would be reworking the script to use something like KUBE_LATEST_VERSION="$(curl -L 'https://dl.k8s.io/ci/latest')"; kind build node-image 'https://dl.k8s.io/ci/'"${KUBE_LATEST_VERSION}"; # fetch the e2e.test etc from releases in the script

/assign
/sig api-machinery

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[aaron-prindle]

Related:

#33980