chore(deps): bump azure/cli from 2 to 3

[dependabot]

Bumps azure/cli from 2 to 3.

Release notes

Sourced from azure/cli's releases.

GitHub Action for Azure CLI v3

What's Changed

• Updated to use node24 by @​thomas-temby in Azure/cli#197

Full Changelog: Azure/cli@v2.2.0...v3

GitHub Action for Azure CLI v3.0.0

What's Changed

• Updated to use node24 by @​thomas-temby in Azure/cli#197

Full Changelog: Azure/cli@v2.2.0...v3.0.0

GitHub Action for Azure CLI v2.2.0

What's Changed

• Mount AZURE_CONFIG_DIR folder instead of ~/.azure by @​MoChilia in Azure/cli#176
• FIX: Broken links by appended dot azcliversion errors by @​nselpriv in Azure/cli#178

New Contributors

• @​nselpriv made their first contribution in Azure/cli#178

Full Changelog: Azure/cli@v2.1.0...v2.2.0

GitHub Action for Azure CLI v2.1.0

What's Changed

• docs: add yaml syntax highlighting to workflow examples by @​baysideengineer in Azure/cli#141
• Fix #153: Prevent stdout cutoff in Azure CLI versions by @​MoChilia in Azure/cli#154

New Contributors

• @​baysideengineer made their first contribution in Azure/cli#141
• @​isra-fel made their first contribution in Azure/cli#151

Full Changelog: Azure/cli@v2.0.0...v2.1.0

Changelog

Sourced from azure/cli's changelog.

Releasing a new version

Semanting versioning is used to release different versions of the action. Following steps are to be followed :

1. Create a new branch for every major version.
   Example, releases/v1, releases/v2.
2. For every minor and patch release for a major version, update the corresponding release branch.
   Example, for releasing v1.1.1, update releases/v1.
3. Create tags for every new release (major/minor/patch).
   Example,v1.0.0. , v1.0.1, v2.0.1, etc. and also have tags like v1, v2 for every major version release.
4. On releasing minor and patch versions, update the tag of the corresponding major version.
   Example, for releasing v1.0.1, update the v1 tag to point to the ref of the current release.
   The following commands are to be run on the release\v1 branch so that it picks the latest commit and updates the v1 tag accordingly : (Ensure that you are on same commit locally as you want to release)

• git tag -fa v1 -m "Update v1 tag"
• git push origin v1 --force

Commits

• 9eb25b8 Release v3.0.0 (#199)
• c1ad804 Add changes (#198)
• 41fca1b Updated to use node24 (#197)
• cbea6ec change the assignee (#191)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.