PowerShell/PowerShell

Instead of building PSReadLine from this repo, pull it from the gallery using nuget cache.

This pulls v2.0 of PSReadLine which does have documented breaking changes from v1.2, but the risk is small - the features that have changed are typically only used in a profile and aren't used all that often anyway.

Fix #996

Hardcodes version of modules pulled from PSGallery

… PowerShell ETW manifest. (#5892)

* Merge and Sort BasicHtmlWebResponseObject

* Merge and sort ContentHelper

…ion that latest version of 3.11 has to be taken (#5926)

* Update recommended WiX toolset link to be generic to WiX 3.x but mention that the latest version of 3.11 has to be taken.

#5923)

* encoding for new-modulemanifest on all platforms should be utf8nobom
* fix test

This is the continuation of PR 5499 that had to be abandoned due to a fatal merge conflict and I did not want to risk accidentally reverting recent fixes.

    Remove unnecessary/unused default for productGuid because it always gets a new Guid when being called from Start-PSPackage
    Add defaults for required files but also add extra path validation attribute
    Rename ProductGuid to ProductCode

…#5907)

…stead of globbing (#5839)

When InitialSessionState initializes it tries to SetLocation to current working directory,
 but if the directory name contains PowerShell wildcard characters, it fails and reverts
 to $PSHOME.
 The change affects Set-Location in that if the path exists (even if containing wildcard characters), just use it. It is a breaking change.

… scope is perMachine. (#5915)

- Add Link controller to WebListener
- Replace HttpListener Link tests with WebListener
- Update WebListener Documentation
- Enable cross-platform multiple Link header tests

- adds type query to Redirect listener and adjusts logic to accommodate
- Replaces HttpListener Redirect Tests with WebListener

)

When calling powershell from powershell (called the minishell for historical reasons), the arguments are passed as a base64 encoded string.

The native command parameter binder was trying to match up the ast to the argument value, which in this case, doesn't make sense.

The Fix is to ignore the ast during parameter binding for this case of calling powershell from powershell.

Fix #5733

…#5875)

…talled by appending " (x86)" for x86 to the . (#5826)

# Conflicts:
#	.github/Images/GitHub-PR.png
#	assets/Product.wxs
#	docs/installation/linux.md
#	docs/installation/macos.md
#	docs/installation/windows.md
#	test/powershell/Modules/Microsoft.PowerShell.Utility/WebCmdlets.Tests.ps1
#	tools/metadata.json

…it for mac (#5843)

* Also, fix syntax issues to allow to work with released Pester

Add a test that has been skipped in PR #5702

…w side by side of x86 and x64. The main menu has a " (x86)" appended to the main menu. (#5824)

Make explorer context menu registry entries platform specific to allow them to work also when both x86 and x64 are installed. The main menu has a " (x86)" appended to the main menu as well.

The symbol resolver was properly resolving the type to the class
definition, but that resolution was ignored at runtime because we used
the string instead of the ITypeName - the ITypeName kept the reference
to the class definition.

Fix #5661