{CI} Add trust brew taps in CI pipeline

[VeryEarly]

Related command

Description

error and suggested fix

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[azure-client-tools-bot-prd]

Hi @VeryEarly,
Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[Copilot]

Pull request overview

Updates the macOS Homebrew formula install step in the Azure Pipelines CI to trust a locally-created non-official Homebrew tap so Homebrew can load the tap’s Ruby code during installation.

Changes:

• Add a brew trust step before installing the generated azure-cli formula from a local dev tap.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[VeryEarly]

By Homebrew's naming convention, a tap repo must be named homebrew- on disk, but the homebrew- prefix is always stripped when Homebrew refers to the tap. So:

dev/azure-cli → tap dev/azure-cli
dev/homebrew-azure-cli → also normalizes to tap dev/azure-cli