WIP DNM git actions,ipam: Bump packages

[oshoval]

What this PR does / why we need it:
Please dont review, trying to debug using this PR.

Special notes for your reviewer:

Release note:

None

[kubevirt-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[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 ask for approval from oshoval. 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]

This might help IPAM, it passed once, where on other PRs it flakes every run lately
in any case those packages are outdated and cause git actions to select different policies (i.e different nodes etc)

rerunning few times

[oshoval]

it didnt help
https://github.com/kubevirt/cluster-network-addons-operator/actions/runs/10758067363/job/29833431320?pr=1879

lets remove KMP from the git action lane, to see if it is resources related

next step is to fix the artifacts collector, as it will hint what happens

[oshoval]

This is weird (unless it is not related to the config below)
https://github.com/kubevirt/cluster-network-addons-operator/actions/runs/10758730777/job/29834484093?pr=1879
it deploys kubevirt 1.3.1

but we still have
testns-27793141b virt-launcher-alpine-641c9b07e-h7wq4 2/3 Error 0 5m
due to guest-console-log container, even that
we are using
kubectl -n kubevirt patch kubevirt kubevirt --type=merge --patch '{"spec":{"configuration":{"virtualMachineOptions":{"disableSerialConsoleLog":{}}}}}'

@akalenyu
can you suggest please ?
should i try latest nighly kubevirt instead ? (but not sure something was fixed after stable kubevirt release 1.3.1
wrt guest-console-log)
EDIT - seems 1.3 does have the logic to bypass it basically

checking if we are using (seems we dont)

	if vmi.Spec.Domain.Devices.LogSerialConsole != nil {
		return *vmi.Spec.Domain.Devices.LogSerialConsole
	}

as it bypass the flag

EDIT ah NVM, we need to add it when using CNAO as well to the CR
sorry for the noise

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[oshoval]

created #1882