Implement PGO in pipelines for AMD64 architecture; supply training test scenarios

[miniksa]

Implement PGO in pipelines for AMD64 architecture; supply training test scenarios

References

• Processing large data is extremely slow (in VMware) #3075 - Relevant to speed interests there and other linked issues.

PR Checklist

• Closes Apply PGO to Binaries #6963
• I work here.
• New UIA Tests added and passed. Manual build runs also tested.

Detailed Description of the Pull Request / Additional comments

• Creates a new pipeline run for creating instrumented binaries for Profile Guided Optimization (PGO).
• Creates a new suite of UIA tests on the full Windows Terminal app to run PGO training scenarios on instrumented binaries (and incidentally can be used to write other UIA tests later for the full Terminal app.)
• Creates a new NuGet artifact to store trained PGO databases (PGD files) at Microsoft.Internal.Windows.Terminal.PGODatabase
• Creates a new NuGet artifact to supply large-scale test content for automated tests at Microsoft.Internal.Windows.Terminal.TestContent
• Adjusts the release pipeline to run binaries in PGO optimized mode where content from PGO databases is leveraged at link time to optimize the final release build

The following binaries are trained:

• OpenConsole.exe
• WindowsTerminal.exe
• TerminalApp.dll
• TerminalConnection.dll
• Microsoft.Terminal.Control.dll
• Microsoft.Terminal.Remoting.dll
• Microsoft.Terminal.Settings.Editor.dll
• Microsoft.Terminal.Settings.Model.dll

In the future, adding <PgoTarget>true</PgoTarget> to a new vcxproj file will automatically enroll the DLL/EXE for PGO instrumentation and optimization going forward.

Two training test scenarios are implemented:

• Smoke test the Terminal by just opening it and typing a bit of text then exiting. (Should help focus on the standard launch path.)
• Optimize bulk text output by launching terminal, outputting big.txt, then exiting.

Additional scenarios can be contributed to the WindowsTerminal_UIATests project with the [TestProperty("IsPGO", "true")] annotation to add them to the suite of scenarios for PGO.

NOTE: There are currently no weights applied to the various test scenarios. We will revisit that in the future when/if necessary.

Validation Steps Performed

• - Training run completed at https://dev.azure.com/ms/terminal/_build?definitionId=492&_a=summary
• - Optimization run completed locally (by forcing PGOBuildMode to Optimize on my local machine, manually retrieving the databases with NuGet, and building).
• - Validated locally that x86 and ARM64 do not get trained and automatically skip optimization as databases are not present for them.
• - Smoke tested optimized binary versus latest releases. big.txt output through CMD is ~11-12seconds prior to PGO and just over 8 seconds with PGO.