chore: disable MultiCIDRServiceAllocator in compat version e2e test as it has known issue with --emulation-version

[aaron-prindle]

Recently the Emulation Version E2E tests started to fail for n-1 and n-2:

https://testgrid.k8s.io/sig-testing-kind#compatibility-version-test-n-minus-1
https://testgrid.k8s.io/sig-testing-kind#compatibility-version-test-n-minus-2

✗ Starting control-plane 🕹️
ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged kind-control-plane kubeadm init --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1

This is related to an issue with the recently graduated feature gate MultiCIDRServiceAllocator and the --emulation-version feature:

PR promoting MultiCIDRServiceAllocator (merged recently): kubernetes/kubernetes#128971

This feature must be disabled for beta when using --emulation-version until we fix kubernetes/kubernetes#127791

This KEP explains the issue and outlines a solution:
kubernetes/enhancements#5038

[aaron-prindle]

/assign @BenTheElder

[aojea]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aaron-prindle, aojea

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

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

[k8s-ci-robot]

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

• key compatibility-versions-e2e.yaml using file config/jobs/kubernetes/sig-testing/compatibility-versions-e2e.yaml

In response to this:

Recently the Emulation Version E2E tests started to fail for n-1 and n-2:

https://testgrid.k8s.io/sig-testing-kind#compatibility-version-test-n-minus-1
https://testgrid.k8s.io/sig-testing-kind#compatibility-version-test-n-minus-2

✗ Starting control-plane 🕹️
ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged kind-control-plane kubeadm init --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1

This is related to an issue with the recently graduated feature gate MultiCIDRServiceAllocator and the --emulation-version feature:

PR promoting MultiCIDRServiceAllocator (merged recently): kubernetes/kubernetes#128971

This feature must be disabled for beta when using --emulation-version until we fix kubernetes/kubernetes#127791

This KEP explains the issue and outlines a solution:
kubernetes/enhancements#5038

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.