treefmt: update checksum for 2.5.0 release

[stefanb]

Goreleaser log histor https://github.com/numtide/treefmt/actions/workflows/release.yml

shows that the v2.5.0 tag was present on 2 commits:

• fist numtide/treefmt@541510b by @brianmcgee
• second numtide/treefmt@7ab41ba also by @brianmcgee

Diff: numtide/treefmt@541510b...7ab41ba is non-trivial.

Ref:

• https://github.com/numtide/treefmt/releases/tag/v2.5.0
• treefmt 2.5.0 #276502
• go 1.27rc2, go@1.26 1.26.5 (new formula) #288803

---

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>?
• Is your test running fine brew test <formula>?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes.

---

[brianmcgee]

Treefmt maintainer here, this was as mistake on my part, nothing nefarious. See numtide/treefmt#711 (comment)

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.