Re-merge Workload Identity Federation (WIF) changes

[bearzz23]

Description

The original PR has already been reviewed before (#25786) but backed out later due to service not being ready. Re-raising this PR to target the October release.

Changelog:

• Added support for Workload Identity Federation and OIDC Issuer features to the ConnectedKubernetes cmdlets.

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
  • For SDK-based development mode, 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.
  • For autorest-based development mode, include the changelog in the PR description.
  • 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]

️✔️Az.Accounts

️✔️Build

️✔️PowerShell Core - Windows

⚠️Az.ConnectedKubernetes

️✔️Build

️✔️PowerShell Core - Windows

️✔️Breaking Change Check

️✔️PowerShell Core - Windows

⚠️Signature Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
⚠️	Get-AzConnectedKubernetes	Get-AzConnectedKubernetes Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzConnectedKubernetes	Get-AzConnectedKubernetes changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.

️✔️Help Example Check

️✔️PowerShell Core - Windows

️✔️Help File Existence Check

️✔️PowerShell Core - Windows

⚠️File Change Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
⚠️		It is required to update ChangeLog.md if you want to release a new version for Az.ConnectedKubernetes.	Add a changelog record under Upcoming Release section with past tense.

️✔️UX Metadata Check

️✔️PowerShell Core - Windows

⚠️Test

⚠️ - Linux

Type	Title	Current Coverage	Last Coverage	Description
⚠️	Test Coverage Less Than 80%	50.00 %	60.00%	Test coverage cannot be lower than the number of the last release.

⚠️ - MacOS

Type	Title	Current Coverage	Last Coverage	Description
⚠️	Test Coverage Less Than 80%	50.00%	60.00%	Test coverage cannot be lower than the number of the last release.

⚠️PowerShell Core - Windows

Type	Title	Current Coverage	Last Coverage	Description
⚠️	Test Coverage Less Than 80%	50.00%	60.00%	Test coverage cannot be lower than the number of the last release.

[msJinLei]

@bearzz23 Please add change log.

[github-actions]

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures.
Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.