fix: update brew before updating matcha

[andrinoff]

This pull request improves the Homebrew upgrade process in the runUpdateCLI function by ensuring that Homebrew taps are updated before attempting to upgrade the matcha package. If updating the taps fails, the process will still attempt the upgrade and print a warning.

Homebrew upgrade process improvements:

• The CLI now runs brew update before brew upgrade matcha, and prints a warning if the update fails but continues to attempt the upgrade.

[Copilot]

Pull request overview

This pull request improves the Homebrew upgrade workflow by adding a brew update step before attempting to upgrade the matcha package. This ensures that Homebrew's formula index is current before the upgrade attempt.

Key Changes:

• Added brew update execution before brew upgrade matcha with graceful error handling
• Updated user-facing message to reflect the additional update step
• Renamed the cmd variable to upgradeCmd for better clarity

Comments suppressed due to low confidence (2)

main.go:1456

• File handle may be writable as a result of data flow from a call to OpenFile and closing it may result in data loss upon failure, which is not handled explicitly.

		out.Close()

main.go:1460

• File handle may be writable as a result of data flow from a call to OpenFile and closing it may result in data loss upon failure, which is not handled explicitly.

	out.Close()

---

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

[Copilot]

The error message refers to "updating taps" but brew update updates more than just taps - it also updates Homebrew itself and all formula/cask definitions. Consider changing this to "Detected Homebrew — updating Homebrew and attempting to upgrade via brew." for accuracy.

Suggested change

	fmt.Println("Detected Homebrew — updating taps and attempting to upgrade via brew.")
	fmt.Println("Detected Homebrew — updating Homebrew and attempting to upgrade via brew.")