Make alias mapping more simple

[maddieclayton]

Description

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate change log has been updated
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • the changes have gone through a cmdlet design review
  • the cmdlet markdown files were generated using the platyPS module

[MiYanni]

I'm still a bit confused... If we made this mapping a json file and included it in our Profile package, wouldn't that work just as well and be significantly easier to understand/maintain? Writing C# code using PowerShell seems a bit over-the-top. Both C# and PowerShell can load the json file and use it as needed.

[maddieclayton]

@MiYanni Done, please take another look - CI will now automatically update the json file instead of the cs file.

[MiYanni]

You'd have to change the Profile .csproj for it to actually include the Mappings.json file. Otherwise, this won't run on someone's machine, right? The file needs to exist for the cmdlet to work.

[MiYanni]

LGTM