ICMP echo reply for every IP from VM

### Description

From colima VM almost every IP responds to ICMP echo (ping). The only exception is IPs from `192.168.5.0/24`, where only 192.168.5.1 and 192.168.5.2 reply.

```
$ ping 5.6.7.8 -c1
PING 5.6.7.8 (5.6.7.8) 56(84) bytes of data.
64 bytes from 5.6.7.8: icmp_seq=1 ttl=64 time=1.62 ms

--- 5.6.7.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.619/1.619/1.619/0.000 ms
```

### Version

colima version 0.7.4
git commit: c2595d464d81a29ebf2e1cf41786c1f05295980c

runtime: docker
arch: aarch64
client: v26.0.2
server: v27.1.1
limactl version 0.23.1
qemu-img version 9.0.2
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

### Operating System

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

### Output of `colima status`

INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/anton/.colima/default/docker.sock

### Reproduction Steps

1. colima ssh
2. apt update && apt install iputils-ping
3. ping 5.6.7.8

### Expected behaviour

Should not see ICMP replies

### Additional context

_No response_

The issue is about unexpected ICMP echo replies from a Colima VM. Start by examining the VM's network configuration and iptables rules. Look at the code that sets up networking in the Colima project, likely in the VM provisioning or network driver. Reproduce the issue by following the steps: SSH into the VM and ping an external IP. Check for any misconfigured proxy ARP or routing that causes the VM to respond to all IPs. Verify the fix by testing pings to IPs outside the local subnet.

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