feat(vm): add IPAM for additional network interfaces

[hardcoretime]

Description

Add IPAM (IP Address Management) for virtual machine additional network interfaces, integrating with the SDN module's IPAM capabilities (address pools, IPAddress resources, DHCP delivery).

Two allocation modes are supported for additional networks that have an IPAM pool (spec.ipam.ipAddressPoolRef):

1. Automatic (DHCP): when ipAddressName is not set in .spec.networks[], the VM controller creates an SDN IPAddress (type Auto) bound to the VM via ownerReferences and passes it to SDN. SDN allocates an address from the pool and delivers it to the guest OS via DHCP. The address is stable across VM restarts and migrations (bound to the VM, not the ephemeral pod).

2. Static: when ipAddressName is set, the controller uses a user-provided IPAddress resource (type Static). The address is determined by the user.

If an additional network does not have an IPAM pool, the feature is not enabled — the interface operates in L2-only mode with manual IP configuration in the guest OS (as before).

The allocated IP address is reflected in status.networks[].ipAddress.

Why do we need it, and what problem does it solve?

Previously, additional network interfaces operated at L2 only — IP addresses had to be configured manually inside the guest OS (e.g., via Cloud-Init). This led to:

• Address conflicts between manually configured IPs and SDN-allocated addresses on the same interface.
• No declarative way to request a specific IP for an additional network (unlike Main network via VirtualMachineIPAddress).
• No IP visibility in VM status for additional interfaces.
• VMs hanging in Starting when network configuration was invalid — CNI d8-sdn fails hard on missing IPAddress, blocking pod creation.

This PR solves these by having the VM controller manage IPAddress resources for additional networks (analogous to VirtualMachineIPAddress for the Main network), with resilient startup (skip problematic interfaces) and reactive reconciliation (watch IPAddress to provision interfaces when addresses become available).

What is the expected result?

• A VM with an additional network that has an IPAM pool receives an IP automatically via DHCP (auto mode) or uses a user-specified static IP (ipAddressName).
• The IP is visible in status.networks[].ipAddress.
• The IP is stable across VM restarts and live migrations.
• If an additional network is misconfigured (e.g., ipAddressName references a non-existent IPAddress, or the network has no pool), the VM starts without that interface and reports the error in the NetworkReady condition.
• Changing ipAddressName (add/remove/switch auto↔static) is applied live without pod recreation or VM restart.
• Creating an IPAddress after VM start triggers reconciliation via watcher — the interface is attached automatically (hotplug).

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: vm
type: feature
summary: "Add IPAM for additional network interfaces: automatic (DHCP) and static IP allocation via SDN IPAddress resources."

[deckhouse-BOaTswain]

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.