Not able to access exposed container port via VM ip address

### Description

Hey there! 👋

First of all, thanks a lot for building Colima. I'm a long time and very happy user.

I noticed that when running Colima in Github Action runners on macOS 15 (Intel) I am not able to reach exposed ports of running containers through the Colima VM ip address. Everything is fine with the macOS 13 (Intel) action runners.

I've been trying to debug it myself, but I exhausted all my networking knowledge (and it's not that deep). Could you help me out in debugging this and potentially finding a solution?

For instance, you can find here (https://github.com/douglascamata/setup-docker-macos-action/actions/runs/19397514275/job/55499598844?pr=57) the logs of a Github Action run that shows the problem. Through the workflow file (https://github.com/douglascamata/setup-docker-macos-action/actions/runs/19397514275/workflow?pr=57) you can see which debug information I'm looking at. If there is any information you think could help in figuring out the problem, let me know and I'll add it there.

I could reproduce the issue in my own macOS machine (Apple Silicon) by connecting to my Tailscale network and using an exit node. It leaves the Colima VM ip address unreachable even when I completely stop Tailscale. The only thing that fixes it is rebooting the Colima VM. I'm not sure if this is related to the issue on Github Action runners, but it's the only potentially useful information I got.

### Version

Colima 0.9.1.

### Operating System

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

### Output of `colima status`

Colima is being started with the following options: `--cpu 4 --memory 14 --arch x86_64 --vm-type=vz --mount-type=virtiofs --network-address --network-preferred-route`

### Reproduction Steps

1. Set up a Github Action workflow that runs on macOS 15 (Intel) and with `--network-address`
2. Start a simple nginx container and map 8080 (host) to 80 (container)
3. Try to curl the nginx exposed web page via the Colima VM ip address.

### Expected behaviour

Request arrives to the nginx container.

### Additional context

_No response_