…le build

Make sure global tool packages are published in stable build

Cherry-picking the checksum changes:
1. #15678
1. #17056

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

Update Ubuntu images to use Ubuntu 20.04 (#15906)

Updated windows.yml

# Conflicts:
#	.vsts-ci/linux-daily.yml
#	test/powershell/Language/Scripting/NativeExecution/NativeStreams.Tests.ps1
#	test/powershell/Modules/PSDesiredStateConfiguration/MOF-Compilation.Tests.ps1
#	test/powershell/Modules/PSDesiredStateConfiguration/PSDesiredStateConfiguration.Tests.ps1

Skip failing scriptblock tests (#17093)
#17093

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

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

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

Disable broken macOS CI job, which is unused

Updated to .NET 3.1.24 / SDK 3.1.418

…16981) to v7.0.10

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

…to CWD locations

Updated files.wxs for 7.0.10

…7.0.10

Making NameObscurerTelemetryInitializer internal

…e - v7.0.10

Fix Generate checksum file for packages build failure

…git versions

Fixed package names verification to support multi-digit versions.

Currently "Validate RPM package names" release step is failing because of version "7.0.10" in these examples:
WARNING: powershell-7.0.10-1.centos.8.x86_64.rpm is not a valid package name
WARNING: powershell-7.0.10-1.rhel.7.x86_64.rpm is not a valid package name
WARNING: powershell-lts-7.0.10-1.centos.8.x86_64.rpm is not a valid package name
WARNING: powershell-lts-7.0.10-1.rhel.7.x86_64.rpm is not a valid package name

Changelog for 7.0.10