Network address does not populate when connected to VPN

### Description

## Preamble
Very sorry if this is a duplicate, I've seen many similar issues on GH and around the web, but none quite like this. Seems like it could be _user_ error, I just didn't have this issue before a macOS update. Thanks for maintaining this otherwise great software!

## Issue
While connected to my corporate VPN I'm unable to connect to docker containers exposed on localhost with a forwarded port.

Notably running `colima ls` displays no network address when the container is spun up on VPN, but does display on VPN. In order to get an accessible container, I have to tediously log out of the VPN, spin it up, then log back in.

## Attempted fixes
- Asking coworker (he gave up and installed podman)
- Setting network address in colima config to true
- Setting network address to false and host addresses to true
- Uninstalling and reinstalling.

### Version

colima version 0.8.1
git commit: 96598cc5b64e5e9e1e64891642b91edc8ac49d16

runtime: docker
arch: aarch64
client: v28.0.0
server: v27.4.0
limactl version 1.0.6
zsh: command not found: qemu-img

### Operating System

- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [x] Apple Silicon >= 14 (Sonoma)
- [ ] Linux

### Output of `colima status`

➜ colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/trpkq59/.colima/default/docker.sock

### Reproduction Steps

1. Sign on to my corporate VPN (sorry...)
2. `docker run` a container with an exposed port
3. Attempt to connect

### Expected behaviour

Connection would be uneventful

### Additional context

This problem may have been introduced with the Sequoia update, but I'm not positive on that.

The issue is about network address detection in colima when a VPN is active. Start by examining the network configuration logic in the colima codebase, likely in files handling VM networking or status reporting. Look for how network interfaces are enumerated and filtered. Test by running colima with VPN on/off and comparing network output. 'Done' means colima displays a network address and containers are reachable while VPN is connected.

Escrito por el modelo de indexación a partir del texto del issue.