[PS] Migrate SecurityInsights module to autorest v4

[JoyerJin]

Description

Preannouncement PR:

• [PS] Add breaking change message for SecurityInsights #28486
• [BC]SecurityInsights Module Breaking Changes Announcement Date Update #29133

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[Copilot]

Pull Request Overview

This PR migrates the SecurityInsights module from AutoRest v3 to v4, updating API models and cmdlet structure. The migration involves significant changes to parameter types, output types, and method signatures to align with the newer AutoRest framework.

Key Changes

• Type simplification from strongly-typed enums to string parameters for improved flexibility
• Output type namespace updates from versioned API models to unversioned ones
• Addition of new parameter sets and JSON-based input methods for cmdlets

Reviewed Changes

Copilot reviewed 150 out of 151 changed files in this pull request and generated 3 comments.

File	Description
tools/StaticAnalysis/Exceptions/Az.SecurityInsights/BreakingChangeIssues.csv	Documents expected breaking changes from the AutoRest v4 migration
Multiple help markdown files	Updated parameter types, output types, and documentation to reflect API changes

[github-actions]

To the author of the pull request,
This PR was labeled "Breaking Change Release" because it contains breaking changes.

• According to our policy, breaking changes can only take place during major release and they must be preannounced.
• Please follow our guide on the detailed steps.
• Required: Please fill in the task below to facilitate our contact,you will receive notifications related to breaking changes.

[Copilot]

Pull request overview

Copilot reviewed 152 out of 153 changed files in this pull request and generated no new comments.

[isra-fel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[NoriZC]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Copilot]

Pull request overview

Copilot reviewed 152 out of 153 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

src/SecurityInsights/SecurityInsights.Autorest/test/Update-AzSentinelOnboardingState.Tests.ps1:24

• Both test cases are marked -skip and contain only a NotImplementedException placeholder, so there is currently no automated coverage for Update-AzSentinelOnboardingState despite the cmdlet being introduced/updated in this PR.

Suggested fix: replace these placeholders with real tests (record/playback or mocking) that execute the cmdlet for the supported parameter sets, and remove -skip once they pass reliably.