ci: remove @semantic-release/github plugin from release config

[jaissica12]

Summary

The release job was failing because @semantic-release/github returned a 404 when creating the GitHub Release. Because that step runs inside npx semantic-release, the non-zero exit failed the whole release job, and the downstream sync-repository job (needs: release) was skipped — leaving main/development un-synced and the release/<n> branch undeleted, even though npm publish and the git tag had already succeeded.

This PR removes the @semantic-release/github plugin from release.config.js. After this change, npx semantic-release performs the full release except creating the GitHub Release:

• works out the next version,
• bumps package.json,
• updates CHANGELOG.md,
• builds and commits dist/ (via scripts/release.sh),
• creates and pushes the git tag,
• publishes to npm (via @semantic-release/exec),

then exits successfully, so the sync-repository job runs and pushes the release commit to main/development and deletes the release branch.

Tradeoff: no GitHub Release entry is created (no Releases-page entry and no dist assets attached there). The git tag and the npm package are unaffected, and a GitHub Release can still be created manually for a given tag if desired (e.g. gh release create v<version> dist/RoktPayPlus-Kit.*).

Testing Plan

• Validated that release.config.js still parses and now resolves to the plugins: commit-analyzer, release-notes-generator, changelog, npm, exec, git (the github plugin is gone).
• Additional testing before merge:
  • Run the Release workflow with dryRun: true and confirm semantic-release completes with no GitHub Release 404.
  • Run a real release and confirm: the npm package publishes, the v<version> tag is pushed, the release job is green, and the sync-repository job runs (pushes to main/development, deletes the release/<n> branch).

[jaissica12]

Closing this in favor of #6