[BUG]: .tool-versions not working in Nushell

[colececil]

Version
0.6.1 (The issue also occurs with the latest commit in main, which is currently b37444af0f.)
OS
Windows

Describe the bug
In Nushell, vfox does not respect .tool-versions files. It just acts as if they aren't there.

Example
In this example, I have my global Node.js version set to 22.12.0. The ~ directory contains no .tool-versions file. In the ~/test directory, I have a .tool-versions file that contains the line nodejs 20.18.3.

Here's what happens in Nushell:

~> node --version
v22.12.0
~> cd `test\`
~\test> open .tool-versions
nodejs 20.18.3
~\test> node --version
v22.12.0

And here's what happens in Git Bash on the same machine:

~$ node --version
v22.12.0
~$ cd test/
~/test$ cat .tool-versions
nodejs 20.18.3
~/test$ node --version
v20.18.3

[colececil]

@bytemain, I just opened this issue for the problem I brought up in #412 the other day. I'm not sure if maybe this has something to do with Nushell using the --full option with vfox env -s, whereas the other shells don't?

As far as I can tell, this is the last remaining issue before we have vfox fully working in Nushell! 🤞 We're almost there!