Pin GoReleaser CLI to ~> v2 instead of 'latest' (#14)

The v1.0.0 release run surfaced:

  You are using 'latest' as default version. Will lock to '~> v2'.

Making the lock explicit avoids silent breakage if GoReleaser ships a v3
with behavior changes. '~> v2' accepts any v2.x release (minor+patch
updates flow in automatically) but blocks a major bump.

Author: drogers0

.github/workflows/release.yml

@@ -25,7 +25,7 @@ jobs:
       - name: Run GoReleaser
         uses: goreleaser/goreleaser-action@v7
         with:
-          version: latest
+          version: "~> v2"
           args: release --clean
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}