Have to disable quiet restore explicitly on local dev machines when
doing a bootstrap build to work around this arcade issue:
https://github.com/dotnet/arcade/issues/2220

* Update PowerShell version

* Exit build.ps1 if PowerShell version less than 5

* Move check, tidy up formatting

This reverts commit 726c2bc0, reversing
changes made to f51b5490.

* Read IBC and VS bootstrapper info from PublishData.json

* Fix IBC directory path

We have two folders we use during a test run: we put our XML result
files in one folder for the Azure DevOps task to specifically catch,
and all other log files in a different folder which we upload as a
generic artifact. We were putting log files in the wrong folder so we
never uploaded them as artifacts.

Nothing other than one suspicious test in SolutionTests.cs used any
of this, so it's easier to move it all and keep things isolated.

* Arcade SDK 1.0.0-beta.19054.11

* Consolidate OptProf scripts

* Use raw IBC data from VSTS drop

This re-establishes our warning only behavior for the build correctness
leg. Fixes a regression introduced in #31913

* Eliminate differences between Arcade and Roslyn targets

* Remove RootNamespace setting as it's overwritten by Core SDK

The point of using the bootstrap compiler is validating that we can
build the C# code base with the latest C# compiler. Unfortunately the
debug version of the compiler is significantly slower than the Release
version and it slows down our Debug unit test runs accordingly.

This change causes us to prefer a release version of the bootstrap
compiler. The debug bootstrap compiler is still used in the determinism
leg hence we wont't lose coverage here. This should bring our Release
and Debug desktop tests back to the same run time.

* Remove RuntimeIdentifier specification

* Arcade directory layout

* Use Arcade testing targets

* Skip CodeStyle tests on Mono

* Include net472 in test target frameworks for Mono

* Remove incorrect file existence check.

* Update ADO integration test yaml

This changes the remaining Jenkins badges on the README to point to our
new Azure DevOps badges instead. Also cleans up a few comments on the
switch over PR

This changes RunTests to always use procdump when tests timeout.

Previously there was a single option, procdumppath, which controlled
both monitoring xunit processes with procdump and using procdump on time
out. The former causes stability issues at times with test execution and
has to be disabled in a couple of places (spanish and integration
tests). The latter has no stability issues and hence should always be
used.