#1692 : Support multiple IP addresses per network interface

[AbhijeetThakur]

What this PR does / why we need it

• I updated the ipAddress field in the VmNetworkInterface model to accept an array of strings instead of just a single string. This change was applied across all migration templates and VMware machines.
• I also refined the user interface logic to support lists of IPs that are separated by commas, ensuring that we validate each IP address individually and display all of them correctly. Additionally, I improved the bulk IP assignment feature so that it flattens the list and checks each IP for validity while keeping track of the validation status for each network interface.

Which issue(s) this PR fixes

fixes #

• Preserve IP for a powered on VM is not getting IPs for multi IP interfaces #1692

Testing done

Screencast.from.16-03-26.10.50.54.PM.IST.webm

[windsurf-bot]

Other comments (2)

• ui/src/features/migration/VmsSelectionStep.tsx (194-204) The `normalizeNetworkInterfaces` function uses `any` type casting which bypasses TypeScript's type checking. Consider updating the function to use proper typing for better type safety.

  const normalizeNetworkInterfaces = (networkInterfaces?: VmData['networkInterfaces']) => {
    if (!networkInterfaces || networkInterfaces.length === 0) return networkInterfaces
    return networkInterfaces.map((nic) => ({
      ...nic,
      ipAddress: Array.isArray(nic.ipAddress)
        ? nic.ipAddress
        : nic.ipAddress
          ? [nic.ipAddress]
          : []
    }))
  }
  

• ui/src/features/migration/RollingMigrationForm.tsx (2749-2749) There's inconsistency in how empty IP values are handled. In some places you're setting `ipAddress: []` and in others you're checking if `ip.trim() !== ''`. For consistency, always use the empty array approach when there's no IP address.

💡 To request another review, post a new comment with "/windsurf-review".