npm install runs into TAR_ENTRY_ERROR EPERM error

### Description

Running `npm install` inside a container on macOS M2 Pro (Ventura) almost always runs into `TAR_ENTRY_ERROR EPERM` error. It potentially has nothing to do with `colima`.

### Version

Colima Version: `0.5.5`
Lima Version: `0.16.0`
Qemu Version: `8.0.3`

### Operating System

- [ ] macOS Intel <= 12 (Monterrey)
- [ ] macOS Intel >= 13 (Ventura)
- [ ] macOS M1 <= 12 (Monterrey)
- [X] macOS M1 >= 13 (Ventura)
- [ ] 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/cc/.colima/default/docker.sock
```
### Reproduction Steps

_No response_

### Expected behaviour

_No response_

### Additional context

While searching for answers, I came across a similar issue on https://github.com/canonical/multipass/issues/2528
And increasing the maxfiles limit solves the issue. Just mentioning this here in case anyone runs into the issue. This issue can also be potentially closed if the fix doesn't involve any changes in `colima`