[EventHub]: Deprecating MSI properties for breaking change release

[damodaravadhani]

Description

Deprecating older MSI properties from Set-AzEventHubNamespace and New-AzEventHubNamespace.

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)
    • https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/1190
  • the markdown help files have been regenerated using the commands listed here

[wyunchi-ms]

Please fix the breaking change exceptions and resolve the conflicts.

[damodaravadhani]

Do you mean suppress the exceptions ? because we want these breaking changes in.

[wyunchi-ms]

Do you mean suppress the exceptions ? because we want these breaking changes in.

Yes, and please resolve the conflicts.

[wyunchi-ms]

Yes, you can append the exceptions throwed from static analysis to the BreakingChange.csv to pass the CI check.

[wyunchi-ms]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wyunchi-ms]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).