feat: Alias and Breakingchange through PSA

[Alex-Sol]

Description

1. Alias
2. Upcoming Breaking Change

---

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• 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:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • {Please put the link here}
  • the markdown help files have been regenerated using the commands listed here

[isra-fel]

Please write a markdown file about how to generate alias spec and breaking change spec. Put it in docs/

[isra-fel]

Known issues:

• PowerShellProcess.getSystemModulePath() does not get correct result -- C:\Users\yeliu\Documents\PowerShell\Modules is not in the result
  • root cause: it gets the module path of windows powershell
  • work-around: install via windows powershell with -Scope AllUsers
• build.proj is packed into installer package
  • fix: add files that should not be packed into .vscodeignore

[YanaXu]

/azp where

[YanaXu]

/azp where

[YanaXu]

/azp where

[azure-pipelines]

Azure DevOps orgs getting events for this repository:

• azclitools

[YanaXu]

/azp list

[azure-pipelines]

CI/CD Pipelines for this repository:

• azure-powershell-migration - vscode-extension
• azure-powershell-migration - security-scan
• azure-powershell-migration - sign

[YanaXu]

/azp run

[azure-pipelines]

Pull request contains merge conflicts.