Fix release pipeline

…le build

Make sure global tool packages are published in stable build

Cherry-picking the checksum change:
#17056

Update the link for downloading the dotnet-install.ps1 link for CI.

… can be resolved to CWD locations

The problem is .NET will return empty strings for special folders that don't exist in some accounts (like System account), and the module path code appends path locations without first checking if the root path is non-empty.  This results in partial paths in the PSModulePath list, which are then interpreted by .NET file APIs as rooted in the current working directory.  And this in turn can allow low privilege users to drop modules in locations that higher privilege accounts will load from, thus gaining escalated privilege code execution.

These changes detect this non-rooted condition and prevents partial paths from being included in search lists.

Cherry picked from !17201

Re-enable `PowerShellGet` tests targeting PowerShell gallery (#17062)

# Conflicts:
#	test/powershell/Modules/PackageManagement/PackageManagement.Tests.ps1

Updated to .NET 6.0.4 / SDK 6.0.202

…al tool

Updated
<PackageReference Include="System.Net.Http.WinHttpHandler" Version="6.0.0" />
to
<PackageReference Include="System.Net.Http.WinHttpHandler" Version="6.0.1" />

… v7.2.3

Updated cgmanifest.json by findMissingNotices.ps1 -Fix

…16981) to v7.2.3

Do not include node names when sending telemetry. (#16981)
#16981

Updated ThirdPartyNotices for 7.2.3

Updated files.wxs for 7.2.3

…7.2.3

Making NameObscurerTelemetryInitializer internal

Changelog for 7.2.3