Add Suggestion information when Modules are renamed or deprecated due to authors moving onto other work

Summary of the new feature / enhancement

Currently there is no mechanism for when modules are renamed to aid in the discoverability of the new name of the module, nor is there in the Gallery a way (that I know of) for a request of merging the results from Module A & Module B together when it is just a simple rename.

I propose to add to PSResourceGet (& would love it backported to PowerShellGet) the ability for some metadata based checking to surface a message to a user when a module has been renamed, completely deprecated or archived. This would be based on giving guidance on adding a new set of tags to modules as part of this process so that this aids discoverability going forward, both for managed deprecations and as optionally giving out recommendations on similar modules too.

These tags perhaps should be & would be added into the existing tags array in the PSD1
Deprecated perhaps paired with NewModuleName:NewModuleName & this in the new module DeprecatedModule:OldModuleName
Archived perhaps paired with 1/more of SuggestedModule:OtherModuleName

Doing so would aid further in discoverability and provide an easier to query graph link that could potentially be optimised on backend calls to the gallery's database layer, whilst, if done correctly, likely would provide opportunity for an interesting set of data to view as use of the gallery continues to grow.

This is based on my comment for this as a strategy going forward, after a number of rethinks on how I think it best to achieve this painful process.

Proposed technical implementation details (optional)

When as user runs Find-PSResource for a module that has been deprecated, it returns a suggestion item as well for any module that has been suggested by the author of the module that has been searched for.

An Example would be for ThreadJob which is now replaced by Microsoft.PowerShell.ThreadJob
Results would be returned for both ThreadJob and Microsoft.PowerShell.ThreadJob

If a User instead Install-PSResource for the deprecated module they should ideally be prompted with one/more modules that have been provided

An example might be that a module like PoshRSJobs had deprecated and recommended

An Example for say the InvokeBuild Module would be to also return suggestion item for ModuleBuilder any other similar projects too.

No files or tests are named. Start by reviewing the existing Find-PSResource and Install-PSResource behavior, then clarify how Deprecated, Archived, NewModuleName, DeprecatedModule, and SuggestedModule tags should be interpreted. Done should include an agreed user-facing behavior for renamed, deprecated, and archived modules.