ci(release-please): skip GitHub Release creation; release.yml owns it (#9)

release-please was about to collide with release.yml on GitHub Release
creation; release.yml's idempotent skip-if-exists would have left the
tarball asset off. With `skip-github-release: true`, release-please owns
version bump + CHANGELOG + tag, release.yml owns the GitHub Release with
tarball + npm publish.

## Test plan

- [x] YAML valid
- [ ] After merge: release-please re-runs (push to main triggers it),
updates PR #8 (no version-content change since v1.2.1 is still the
calculated bump)
- [ ] Merging PR #8 creates v1.2.1 tag (release-please) WITHOUT a GitHub
Release
- [ ] release.yml fires from tag push, creates GitHub Release v1.2.1
with the tarball asset, then OIDC-publishes to npm

Author: nalyk

.github/workflows/release-please.yml

@@ -31,3 +31,9 @@ jobs:
           token: ${{ secrets.GITHUB_TOKEN }}
           config-file: release-please-config.json
           manifest-file: .release-please-manifest.json
+          # release-please owns: version bumps, CHANGELOG entries, the v<X.Y.Z>
+          # tag created on PR merge. release.yml owns: building + smoke-testing
+          # the tarball, creating the GitHub Release WITH that tarball as an
+          # asset, and OIDC-publishing to npm. Skipping the bot's own GitHub
+          # Release here prevents the two from colliding.
+          skip-github-release: true