ci: retrigger release workflow after suppression token in #175 body (#176)

PR #175 body referenced the semantic-release suppression token
verbatim while documenting what the dropped @semantic-release/git
plugin used to emit. The squash-merge commit message inherited that
verbatim quote and the release workflow was silently skipped, so the
fix from #175 itself never reached npm.

This is a no-op commit whose title and body do not contain the
literal suppression token, so the next push event triggers the
release workflow normally. Same recovery pattern used after PR #171.

Also expanded the workflow header comment to note that #175 hit the
same gotcha — small breadcrumb for the next person.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Author: JonasJesus42

.github/workflows/release.yml

@@ -15,7 +15,7 @@ name: Release
 # semantic-release skip token") instead of pasting the literal.
 #
 # Recover with a no-op commit whose entire message — title and body
-# — does NOT contain the literal token.
+# — does NOT contain the literal token. Past occurrences: #171, #175.
 #
 # References:
 #  - https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs