Update upgrade notification message

[SteveL-MSFT]

PR Summary

If terminal doesn't support VT, no colors are used. Also added aka.ms shortcut. Padding had to be calculated to make sure it looks nice which means
if the message line lengths change, the code may need to be updated as it expects the first line to be longest and the first and last line to include
the release tag. The stable version is the same but the word stable in place of preview.

Before:

After:

PR Context

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:
• 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).

[SteveL-MSFT]

@PoshChan please retry static

[PoshChan]

@SteveL-MSFT, successfully started retry of PowerShell-CI-static-analysis

[TylerLeonhardt]

Due to feedback from another PR I strongly encourage not going with the hard-coded yellow

[TylerLeonhardt]

Also, this would be the second location the inverse escape sequence is hard coded in our code... We need to figure out what we're going to do about that in the future.

[iSazonov]

Coloring is very sensitive area. Windows has a special team for this. I'd prefer classic color scheme. This color kaleidoscope is distracting and annoying.
What will be next? Advertising banners? :-)

[iSazonov]

Coloring is nice for demo on a conference stand. For normal daily work, when the console is started dozens of times, it can tire your eyes.
Unix utilities have --color key but not pwsh.
I don’t like that we began to saturate the codewith color without a common approach.

[SteveL-MSFT]

@PoshChan please retry static

[PoshChan]

@SteveL-MSFT, successfully started retry of PowerShell-CI-static-analysis

[SteveL-MSFT]

@iSazonov I've started adding more color settings to $host.PrivateData (it's unfortunate that member is named that...) so users can opt out or customize.

[iSazonov]

@SteveL-MSFT I pulled #10778 to fix static CI.

[iSazonov]

I've started adding more color settings to $host.PrivateData (it's unfortunate that member is named that...) so users can opt out or customize.

Oh, it would be great to have modern design (RFC?) - PowerShell is power and I'd expect that we could do coloring gracefully, smart and powershelly :-)

[vexx32]

Agreed. We shouldn't bury it in a $host API unless we also plan on exposing it via a cmdlet when it is reasonably feature-complete. 🙂

Couldn't we store color settings in the settings JSON file?

[SteveL-MSFT]

@vexx32 we should probably have a new issue to discuss that

[iSazonov]

#10780 new issue for coloring.

[daxian-dbw]

@joeyaiello Please review the user experience of the notification message.

[daxian-dbw]

@bergmeister Can you please also review this?

[joeyaiello]

String looks fine to me for now, we can easily iterate it over time. @SteveL-MSFT and I discussed possibly doing an "upgrade doc" that we can point to generically (/cc @sdwheeler) that would describe how updating should be done on each platform.

[bergmeister]

Lgtm, nice colour block