build(deps): bump azure/CLI from 1 to 3

[dependabot]

Bumps azure/CLI from 1 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

GitHub Action for Azure CLI v2

What's Changed

• Update Action to use Node.js v20 by @​eikooc in Azure/cli#126
• Bump dependencies to the latest versions by @​MoChilia in Azure/cli#135

New Contributors

• @​eikooc made their first contribution in Azure/cli#126

Full Changelog: Azure/cli@v1.0.9...v2

GitHub Action for Azure CLI v1.0.9

• Set action failure on a non-Linux-based OS (#123)

GitHub Action for Azure CLI v1.0.8

• Fix #103: Dealing with un-escaped environment variables which cause escalation of privilege (#105)

GitHub Action for Azure CLI v1.0.7

... (truncated)

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)
• 9f7ce6f Release v2.2.0 (#187)
• 1759558 Add changes
• 0af5a2a Fix broken links caused by appended dot in invalid azcliversion errors (#178)
• 3bc077d Add changes
• 48a3fb0 Mount AZURE_CONFIG_DIR folder instead of ~/.azure (#176)
• ce5a2f6 Bump actions/checkout to v4 (#170)
• Additional commits viewable in compare view