PR Summary

Write an InstallLocation registry value to a location specific to the bitness and release tag so that it doesn't change from release to release. Fixes #13573

Build the win7-x64 package and installed to make sure it works correctly. The key should also be documented, but I'm not sure where in this repo that would be - perhaps something separate in your docs repo for docs.microsoft.com, if you have one.

PR Context

Quick fix for a customer issue in which I was mentioned. The customer was using a location that not only changes from version to version, but should not be used because that registry isn't meant for direct consumption. Windows Installer has always taken a very firm stance on, "if it's not documented, it's not supported".

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed: Document new InstallLocation registry value MicrosoftDocs/PowerShell-Docs#6589
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).