cluster: Use --opt-out-kv-ipam

[oshoval]

What this PR does / why we need it:
Make cluster-sync going to install it anyhow.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign maiqueb for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[oshoval]

#8 13.85 >>> Librepo error: Cannot download repomd.xml: Cannot download repodata/repomd.xFailed to download metadata (metalink: "https://mirrors.fedoraproject.org/metalink?repo=rawhide&arch=x86_64") for repository "rawhide"
#8 13.85  Librepo error: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

some hiccup while dnf install

[oshoval]

https://pagure.io/fedora-infrastructure/issue/12183
Fedora issue here
(trying feodra:40 locally meanwhile for the other tasks)

[oshoval]

interesting, flake on unit test (unless something was changed and it will fail consistently)
https://github.com/kubevirt/ipam-extensions/actions/runs/10900433841/job/30248013978?pr=68
i think it is not related to this PR, as it changes only e2e

[maiqueb]

interesting, flake on unit test (unless something was changed and it will fail consistently) https://github.com/kubevirt/ipam-extensions/actions/runs/10900433841/job/30248013978?pr=68 i think it is not related to this PR, as it changes only e2e

Hm, it's the order right ? Do we really need the order of this to be this static ?
If not, we can just use consist of instead of equal in the tests.
@qinqon

[qinqon]

interesting, flake on unit test (unless something was changed and it will fail consistently) https://github.com/kubevirt/ipam-extensions/actions/runs/10900433841/job/30248013978?pr=68 i think it is not related to this PR, as it changes only e2e

Hm, it's the order right ? Do we really need the order of this to be this static ? If not, we can just use consist of instead of equal in the tests. @qinqon

We are not crafting the jsonpatch ourselves, we just pass new and old pods to admission.PatchResponseFromRaw so this is supose to be fine, problem is that at slices order matter when we compare things at tests, even if we compare them as a json.

We have to fix the test so the test case instruct to ignore the order there.