Replace Windows symlinks with volta run scripts

[charlespierce]

Closes #1397

Info

• Huge kudos to @rcsilva83 and @Xstoudi for a bunch of iteration in No more symlinks on Windows #1552 on removing symlinks for Windows, to allow dropping the requirement for Developer Mode.
• Based on discussions in that PR, we had a new idea for replacing symlink shims on Windows by using scripts that call volta run <package>.
• This is a first-pass implementation of creating simple script-based shims for executing 3rd-party binaries on Windows.
• This should be a no-op for Unix.

Changes

• Used junction to create NTFS junctions instead of directory symlinks (this part is directly copied from No more symlinks on Windows #1552)
• Updated the shim module to have different implementations of create for Unix and Windows.
  • The Unix implementation is the same as it was before.
  • The Windows implementation creates a very simple .cmd script that calls volta run for the shim. It also continues to create a custom Git Bash script, though that script is updated to now call volta run directly, instead of calling the existing shim via cmd.exe
• Create a new v4 layout since the shim file on Windows is now <binary>.cmd instead of <binary>.exe.
• Created a migration to v4 that removes and regenerates the shims, making sure that the old symlinks are removed. The migration also updates any existing directory symlinks to use junctions as well.

Tested

• Installed packages using the current Volta version (i.e. with symlinks).
• Installed a new version of Volta based on these changes.
• Verified that running the existing packages still works and that the shims were properly migrated.
• Turned off developer mode.
• Verified that even without developer mode, I could install and run new packages 🎉
• Did some very basic performance tests, on my local machine I wasn't seeing any statistically significant differences between the symlink-based approach and the volta run approach ⚡

[Xstoudi]

Hey @charlespierce, great work!

Did you find time to check how it affects performance?
How much time do you think is needed to merge/release? Tbh this is somehow a go/no-go to use Volta in entreprise-grade Windows environment.

I'd be happy to help if some more work is needed to go forward with it, let me know.

[charlespierce]

Was able to get some testing done, and from what I can tell it doesn't have any major effect on performance, so this should be good to go 🎉

[chriskrycho]

For posterity, this is the only difference between the v3 and v4 layouts, and this is the diff:

    pub fn shim_file(&self, toolname: &str) -> PathBuf {
-       path_buf!(self.shim_dir.clone(), executable(toolname))
+       // On Windows, shims are created as `<name>.cmd` since they
+       // are thin scripts that use `volta run` to execute the command
+       #[cfg(windows)]
+       let toolname = format!("{}{}", toolname, ".cmd");
+
+       path_buf!(self.shim_dir.clone(), toolname)
    }