Adding AlertsSuppressionRule cmdlets to Az.Security

[nitsi]

Description

Adding new capabilities for alerts suppression rule - user can create, delete, update and get rules (create and update are both the same "Set").

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)
    • design review
  • the markdown help files have been regenerated using the commands listed here

[isra-fel]

Please resolve the conflicts

[nitsi]

@isra-fel I'm getting the following error:
"Az.Security","Microsoft.Azure.Commands.Security.Cmdlets.AlertsSuppressionRules.NewAlertsSuppressionRuleScope","New-AzAlertsSuppressionRuleScope","1","8100","New-AzAlertsSuppressionRuleScope Does not support ShouldProcess but the cmdlet verb New indicates that it should.","Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue"

NewAlertsSuppressionRuleScope has SupportsShouldProcess = false do I need to support ShouldProcess in this case, as it creates a local variable not a remote resource?

[isra-fel]

@nitsi no, in-memory cmdlets do not support ShouldProcess.
CI failed simply because the rule was set to detect by cmdlet name (verb).
Please follow this guide to suppress the error: https://github.com/Azure/azure-powershell/blob/main/documentation/Debugging-StaticAnalysis-Errors.md#breaking-changes

[nitsi]

@isra-fel tests and static analysis passed, "azure-powershell - security-tools" have not started yet (2h), is there a way to restart it?

[isra-fel]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[nitsi]

@isra-fel all pipelines finished successfully over an hour ago, what is the next step?