Timestamp issue in mounted volume

### Description

I'm running into a strange issue if I mount a folder from the native OS. In a mounted folder, frequently I'm unable to untar folders. This is particularly problematic if I'm using vcpkg because I have less control over that system.

### Version

colima version 0.7.3
git commit: a66b375e8df84ff2860797efc683e66632bcbce3

runtime: docker
arch: x86_64
client: v27.1.2
server: v27.1.1
limactl version 0.23.1
qemu-img version 9.0.2

### Operating System

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

### Output of `colima status`

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

### Reproduction Steps

1. curl -L -o facebook-zstd-v1.5.6.tar.gz https://github.com/facebook/zstd/archive/refs/tags/v1.5.6.tar.gz
2. tar -xvf facebook-zstd-v1.5.6.tar.gz
3. failure

using tar -mxvf facebook-zstd-v1.5.6.tar.gz works as expected since its ignoring mod time

copying to an unmounted folder and running tar -xvf facebook-zstd-v1.5.6.tar.gz does not give the error

### Expected behaviour

The files extract without error

### Additional context

image is almalinux 8.9 although I don't believe image matters

The issue involves timestamp handling in mounted volumes with sshfs. Start by examining the mount implementation in Colima, likely around the SSHFS mount driver. Look for timestamp synchronization or file attribute handling. Reproduce the issue locally by mounting a folder and attempting to untar the provided zstd archive. Check logs and compare behavior between mounted and unmounted directories to isolate the timestamp discrepancy.

Rédigé par le modèle d'indexation à partir du texte de l'issue.