Node InternalIP may not be the same as Server networkInterfaces

[defo89]

What happened:
During server discovery metalprobe posts network interfaces and IPs information which is stored in:

• Server .status.networkInterfaces
• boot operator ipxebootconfig and httpbootconfig .spec.systemIPs

User (capi, gardener) may want to run production server on other network/subinterface/LAG (which is different from discovery) when providing a claim with appropriate ignition.

In this case node's InternalIP should not be the same as Server's .status.networkInterfaces

[afritzler]

The wrong IP detection has been addressed here ironcore-dev/metal-operator#112

Regarding the custom IP allocation of a Server: Here we need to extend the Server machinery to allow custom IP allocation for a Servers network interfaces.