Is your feature request related to a problem? Please describe.
Currently, tenv writes the lock file within the same folder used for tools version storage, meaning the TENV_ROOT, when doing so, tenv creates the .lock file in exclusive mode using O_EXCL, that works fine until the point where TENV_ROOT is represent by a filesystem that does not support exclusive mode, like for example, if your are using https://github.com/awslabs/mountpoint-s3 to mount the filesystem to a S3 bucket.

Describe the solution you'd like
Ideally, it would be nice if tenv could decouple the tools storage from the lock file, allowing the lock file to be written to a different folder.

Describe alternatives you've considered
I could have a process that syncs all tools version to the mountpoint, so the cache will be always hot, preventing tenv from having to install the version and therefore not activating the locking logic.

Additional context
Add any other context or screenshots about the feature request here.