Ran into small issue with a prefix for Get-Metadata for the first time.

[codypaternostro]

I was reading about the VMS command prefix after having my first conflict with Get-Metadata. I wanted to install a configuration module that had the same command Get-Metadata. As a simple solution, I could prefix the command myself and move on, but that might cause issues down the line.

I wanted to suggest a idea that the current set of commands use the appdata path for connection profiles to possibly store the history of the user's current list of commands as a point of reference. Then, a module-wide switch/boolean value set could detect commands not using the VMS prefix and modify them locally. If a user ever wanted to switch back, they could either reinstall the module or use the saved history to restore to the original.

This idea may be too intense, but an alternative solution may exist. Please share what you think!

[joshooaj]

FYI - I'm looking to rename/remove commands/aliases with name collisions in an upcoming release #171