When using AGENT_E2E_TEST_BOOT_MODE=ISO_NO_REGISTRY` with `AGENT_E2E_TEST_SCENARIO=COMPACT_IPV4`, the scripts create a "hosts" file that lists where each node should be located on the network. However, the IP
addresses written to this file don't match the actual IP addresses the nodes get when they boot up.

For example: The hosts file says: `"master-0 is at 192.168.111.80"` but the actual node gets: `192.168.111.20`

This happens because:
1. When the scripts write the hosts file, they assume nodes will use static IPs starting at `.80`
2. But in `ISO_NO_REGISTRY` mode, the ISO doesn't include any network configuration
3. So when nodes boot up, they fall back to DHCP (automatic IP assignment)
4. The DHCP server gives them IPs starting at `.20` instead
5. Later, when scripts try to connect to nodes using the hosts file, they try `.80` but the node is actually at `.20` - connection fails!

In the regular ISO mode, the scripts pre-configure static IP addresses (like .80, .81, .82) directly into the ISO image. When nodes boot from that ISO, they use those exact IPs. So everything matches up perfectly. `ISO_NO_REGISTRY` mode is different - it creates a standalone ISO that doesn't have any pre-configuration, so nodes just grab whatever DHCP gives them.