test(cli): update local package snapshots

Author: Salnika

packages/cli/snap-tests-global/env-install-binary-conflict/snap.txt

@@ -1,41 +1,41 @@
 > vp install -g ./env-binary-conflict-pkg-a # Install pkg-a which provides env-binary-conflict-cli binary
 info: Installing 1 global package with Node.js <semver>
-✓ Installed ./env-binary-conflict-pkg-a <semver>
+✓ Installed env-binary-conflict-pkg-a <semver>
   Bins: env-binary-conflict-cli
 
 > cat $VP_HOME/bins/env-binary-conflict-cli.json # Bin config should point to pkg-a
 {
   "name": "env-binary-conflict-cli",
-  "package": "./env-binary-conflict-pkg-a",
+  "package": "env-binary-conflict-pkg-a",
   "version": "1.0.0",
   "nodeVersion": "22.22.0",
   "source": "vp"
 }
 [1]> vp install -g ./env-binary-conflict-pkg-b # Try to install pkg-b without force - should fail
 info: Installing 1 global package with Node.js <semver>
-error: Failed to install ./env-binary-conflict-pkg-b: Executable 'env-binary-conflict-cli' is already installed by ./env-binary-conflict-pkg-a
+error: Failed to install env-binary-conflict-pkg-b: Executable 'env-binary-conflict-cli' is already installed by env-binary-conflict-pkg-a
 
-Please remove ./env-binary-conflict-pkg-a before installing ./env-binary-conflict-pkg-b, or use --force to auto-replace
+Please remove env-binary-conflict-pkg-a before installing env-binary-conflict-pkg-b, or use --force to auto-replace
 
 > cat $VP_HOME/bins/env-binary-conflict-cli.json # Bin config should still point to pkg-a
 {
   "name": "env-binary-conflict-cli",
-  "package": "./env-binary-conflict-pkg-a",
+  "package": "env-binary-conflict-pkg-a",
   "version": "1.0.0",
   "nodeVersion": "22.22.0",
   "source": "vp"
 }
 > vp install -g --force ./env-binary-conflict-pkg-b # Force install pkg-b - should auto-uninstall pkg-a
 info: Installing 1 global package with Node.js <semver>
-Uninstalling ./env-binary-conflict-pkg-a (conflicts with ./env-binary-conflict-pkg-b)...
-Uninstalled ./env-binary-conflict-pkg-a
-✓ Installed ./env-binary-conflict-pkg-b <semver>
+Uninstalling env-binary-conflict-pkg-a (conflicts with env-binary-conflict-pkg-b)...
+Uninstalled env-binary-conflict-pkg-a
+✓ Installed env-binary-conflict-pkg-b <semver>
   Bins: env-binary-conflict-cli
 
 > cat $VP_HOME/bins/env-binary-conflict-cli.json # Bin config should now point to pkg-b
 {
   "name": "env-binary-conflict-cli",
-  "package": "./env-binary-conflict-pkg-b",
+  "package": "env-binary-conflict-pkg-b",
   "version": "2.0.0",
   "nodeVersion": "22.22.0",
   "source": "vp"

packages/cli/snap-tests-global/npm-global-install-already-linked/snap.txt

@@ -3,7 +3,7 @@
 
 > vp install -g ./npm-global-linked-pkg # First install via vp (creates managed shim)
 info: Installing 1 global package with Node.js <semver>
-✓ Installed ./npm-global-linked-pkg <semver>
+✓ Installed npm-global-linked-pkg <semver>
   Bins: npm-global-linked-cli
 
 > npm-global-linked-cli # Should be callable via the link

packages/cli/snap-tests-global/npm-global-uninstall-vp-managed/snap.txt

@@ -1,6 +1,6 @@
 > vp install -g ./npm-global-vp-managed-pkg # Install via vp (creates managed shim)
 info: Installing 1 global package with Node.js <semver>
-✓ Installed ./npm-global-vp-managed-pkg <semver>
+✓ Installed npm-global-vp-managed-pkg <semver>
   Bins: npm-global-vp-managed-cli
 
 > npm install -g ./npm-global-vp-managed-pkg # npm install (should warn about conflict)

packages/cli/snap-tests-global/shim-recursive-package-binary/snap.txt

@@ -1,6 +1,6 @@
 > vp install -g ./recursive-cli-pkg # Install test package
 info: Installing 1 global package with Node.js <semver>
-✓ Installed ./recursive-cli-pkg <semver>
+✓ Installed recursive-cli-pkg <semver>
   Bins: recursive-cli
 
 > recursive-cli # Outer call triggers recursive inner call through shim