pluto: update checksum for 5.24.0.release

[stefanb]

Github actions log https://github.com/FairwindsOps/pluto/actions/workflows/github-action-test.yml

indicates that the tag v5.24.0 was present on at least 2 commits:

• first FairwindsOps/pluto@c85f54c pushed by @vitorvezani, picked up by pluto 5.24.0 #279700
• second FairwindsOps/pluto@dd5ec8c, also pushed by @vitorvezani and used now for https://github.com/FairwindsOps/pluto/releases/tag/v5.24.0

Diff FairwindsOps/pluto@c85f54c...dd5ec8c shows just goreleaser config changes.

Ref:

• https://github.com/FairwindsOps/pluto/releases/tag/v5.24.0
• pluto 5.24.0 #279700
• 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.

---

[SMillerDev]

Doesn't explain why they retagged though

[stefanb]

Doesn't explain why they retagged though

Diff FairwindsOps/pluto@c85f54c...dd5ec8c explains it: to adjust goreleaser config to fix the

• release signatures and
• signature verification instructions in the generated release notes footer

not enough? It seems understandable that they wanted to quickly adjust the existing release instead of properly tagging a new one.

[SMillerDev]

Who says it was actually them that changed the signing settings? Homebrew's policy is to treat changing tags as an upstream security issue unless confirmed otherwise by upstream. Just because we can assume it was intentional does not make it benign.

[stefanb]

Retagging confirmed upstream in

• 5.24.0 seems to have been retagged. FairwindsOps/pluto#601