ci(release): replace fetch-tags with fetch-depth:0 in checkout

The push-tag trigger that fired for v0.0.2 failed with

  Cannot fetch both ef6dffd... and refs/tags/v0.0.2 to refs/tags/v0.0.2

— a known interaction in actions/checkout@v4 where `fetch-tags: true`
combined with a tag ref tries to fetch the same ref twice. Switching to
`fetch-depth: 0` gives the resolve-tag step the full history it needs
without the duplicate-fetch conflict.

(The release.yml flow itself is unchanged; this only fixes the runner
side.)

Author: Sunrisepeak

.github/workflows/release.yml

@@ -27,11 +27,15 @@ jobs:
       # so we pin to a known path.
       MCPP_HOME: /home/runner/.mcpp
     steps:
-      # fetch-tags so the resolve-tag step can detect existing tags
-      # without an extra round-trip; full history isn't needed.
+      # fetch-depth: 0 instead of fetch-tags: true — actions/checkout@v4
+      # fails on push-tag triggers when both the ref'd tag and
+      # `fetch-tags: true` are set:
+      #   "Cannot fetch both <sha> and refs/tags/vX.Y.Z to refs/tags/vX.Y.Z"
+      # Full-history fetch covers the resolve-tag step's needs without
+      # that contention.
       - uses: actions/checkout@v4
         with:
-          fetch-tags: true
+          fetch-depth: 0
 
       - name: Resolve target tag + commit
         id: resolve