Fixes issue#8468: npm.ps1 and npx.ps1 fail on Windows PowerShell 5.1 when run in strict mode.

…ve URL (#8473)Fix an issue where the configured registry protocol does not follow whenresolving a package resolved url.## ReferencesFixes#8472Co-authored-by: Jean-Philippe Boucher <jeanphilippe.boucher@cauca.ca>

This reverts commitc8d8397.

…8534)fixes#8342WhatThis PR fixes an issue where npm fails to properly handle transitivefile dependencies when using the --install-links flag. Previously, whena file dependency had its own file dependencies, npm would fail toresolve them correctly, resulting in `ERR_MODULE_NOT_FOUND` errors.WhyWhen using `npm install --install-links` to install a local package thathas its own file dependencies, npm would attempt to resolve thetransitive dependencies relative to the installed location in`node_modules` rather than the original source location. This caused theinstallation to fail because the transitive dependencies couldn't befound at the incorrect path.For example, given this structure:Running `npm install --install-links ../b` from `mainpkg` would failbecause npm tried to find a relative to `b` instead of relative to theoriginal `b` source location.HowThe fix introduces logic to detect transitive file dependencies when`--install-links` is used and ensures they are resolved relative totheir parent's original source location:Detect transitive file dependencies: When a parent package was installed(not linked) due to `--install-links` and has file dependencies of itsown, those are identified as transitive file dependencies.Preserve original paths: The parent's resolved` field (e.g., file:../b)is used to determine the original source location.Correct path resolution: Transitive file dependencies are resolvedrelative to the parent's original location rather than its installedlocation in `node_modules`

`node.parent` is resulting in `null` value somewhere in recursive/loopedcalls to `#loadPeerSet` method in building ideal tree.When circular peer ref of a top level dependency replaced/resolved withdifferent compatible version, it makes top level dependency to beremoved from it's parent ( node.parent = null ) since it's beenreplaced, so no longer need to proceed with further peer setexploration.fixes:#8261

Fixes#8528

improve the argument parsing PS1 logic- support `& npm args` and `. npm args` properly- support syntax such as `C:\"Program Files"\nodejs\npm.ps1 args`**of course ^ for both npm and npx version of the script**Code Explanation: instead of getting the `CommandElements.Extent.Text`array and joining it with spaces right away, now it's getting the samearray and only capturing everything after the first element

<!-- What / Why -->This solves problem described in#8335 in a backwards-compatible way.<!-- Describe the request in detail. What it does and why it's beingchanged. -->This PR adds possibility to have env var replacements in .npmrc configswritten as `${VAR?}` which will cause them to get replaced with an emptystring if the variable is not defined. Old behavior where undefinedvariables are left unreplaced is not changed.## References<!-- Examples:  Related to #0  Depends on #0  Blocked by #0  Fixes #0  Closes #0-->Fixes#8335---------Co-authored-by: Michael Smith <owlstronaut@github.com>

While investigating CI failure in#8537,I found unrelated test failures when running locally on windows.`prune with lockfile with implicit optional peer dependencies` fixed byadding files to fixture `node_modules`, avoiding network, also reducedpackage lock to minimum and removed unhelpful snapshots`move aside symlink clutter` fixed by creating problematic symlink in`t.testdir()` instead of in `reifyPackages` hook---------Co-authored-by: Liam Mitchell <liam.mitchell@mendix.com>