fix: remove unsupported after hooks from GoReleaser v2 config

[Copilot]

GoReleaser v2 dropped the global after hooks field, causing the release job to fail immediately with a YAML unmarshal error.

Changes

• .goreleaser.yml: Remove the after hooks section and the cp plugin.json plugin.json.orig backup step — the after block was solely restoring plugin.json post-build, which is unnecessary in a CI environment where the working directory is discarded after the job.

# Before
before:
  hooks:
    - "cp plugin.json plugin.json.orig"
    - "sed -i.bak 's/\"version\": \".*\"/\"version\": \"{{ .Version }}\"/' plugin.json && rm -f plugin.json.bak"
after:
  hooks:
    - "mv plugin.json.orig plugin.json"

# After
before:
  hooks:
    - "sed -i.bak 's/\"version\": \".*\"/\"version\": \"{{ .Version }}\"/' plugin.json && rm -f plugin.json.bak"

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This PR updates the repository’s GoReleaser v2 configuration to remove an unsupported global after hooks block that causes the release workflow to fail during YAML unmarshalling.

Changes:

• Removed the global after.hooks section from .goreleaser.yml (unsupported in GoReleaser v2).
• Removed the now-unneeded cp plugin.json plugin.json.orig backup/restore flow, leaving only the before.hooks version substitution.

---

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