ipam: Adapt to ipam-controller renaming and repo transfer

[oshoval]

What this PR does and why is it needed

Since ipam component was renamed to kubevirt-ipam-controller, and also the repo URL was changed (to https://github.com/kubevirt/ipam-extensions) we need to adapt to those changes.

Which issue(s) this PR fixes

Fixes #

Special notes for reviewers

How to verify it

Details to documentation updates

Description for the changelog

Does this PR introduce a user-facing change?

[oshoval]

failures doesnt seem related to the deployment was tested also on ipam-controller itself https://github.com/kubevirt/ipam-extensions/pull/35#issuecomment-2193738235

[ovn-robot]

Oops, something went wrong:

Must have admin rights to Repository.

[qinqon]

/lgtm

[oshoval]

rebased

[tssurya]

opened control plane EFW flake: https://github.com/ovn-org/ovn-kubernetes/issues/4480 upgrade flake: https://github.com/ovn-org/ovn-kubernetes/issues/4481