fix: Update minikube prow job to use community cluster

[rjsadow]

This PR transitions the pull-minikube-build job from the default cluster to eks-prow-build-cluster

ref: #29722

[rjsadow]

@kubernetes/sig-cluster-lifecycle-leads for this transition to the community owned cluster, CPU/memory reqs and limits are required. I've set them initially to .5CPU and 2GB respectively. Let me know if this seems apropriate.

[rjsadow]

/hold for review from @kubernetes/sig-cluster-lifecycle-leads

[neolit123]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neolit123, rjsadow

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:

• config/jobs/kubernetes/minikube/OWNERS [neolit123]

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

[rjsadow]

/remove-hold

[ameukam]

/lgtm

[k8s-ci-robot]

@rjsadow: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key minikube.yaml using file config/jobs/kubernetes/minikube/minikube.yaml

In response to this:

This PR transitions the pull-minikube-build job from the default cluster to eks-prow-build-cluster

ref: #29722

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.