fix(vm): stabilize the order of network interfaces

[LopatinDmitr]

Description

This PR stabilize the order of network interfaces:

• API: Add optional id field to NetworksSpec and NetworksStatus so each network entry has a stable identifier.

• Controller: Introduce MacAddressPool and ID-based logic in CreateNetworkSpec: MACs are bound to network name (from status), so reusing the same spec entries (with same IDs) after removal preserves MACs and interface names. Allocate and persist network IDs in the reconciler; validators enforce that existing IDs are immutable and in range 1–16383.

• e2e: Add test “verifies interface name persistence after removing middle ClusterNetwork”: create VM with Main + two ClusterNetworks, record last interface name via SSH, remove the middle ClusterNetwork from spec (keeping first and third entries so IDs are preserved), reboot via VMOP, then assert the last interface name is unchanged.

Example spec before (Main + two ClusterNetworks):

spec:
  networks:
    - type: Main
      id: 1
    - type: ClusterNetwork
      name: cn-1003-for-e2e-test
      id: 2
    - type: ClusterNetwork
      name: cn-1004-for-e2e-test
      id: 3

After removing the middle network, user keeps the same structs for the remaining networks so IDs (and thus MACs/interface names) stay stable:

spec:
  networks:
    - type: Main
      id: 1
    - type: ClusterNetwork
      name: cn-1004-for-e2e-test
      id: 3

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

When a VM has several additional networks (e.g. Main + two ClusterNetworks) and the user removes one of them from spec.networks, the controller re-builds the interface list. Without stable IDs, the remaining networks could get new MAC addresses and thus new interface names inside the guest (e.g. eth2 becoming eth1). That breaks guest-side configuration (scripts, Netplan, static IPs) and complicates automation.

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: fix
summary: "Stabilize the order of network interfaces"

[danilrwx]

any id uniqueness checks?

[LopatinDmitr]

any id uniqueness checks?

Fixed it