fix: repair npm trusted publishing workflow

[TDanks2000]

What

• run releases on Node 24 instead of Node 20
• install npm 11.18.0 so npm trusted publishing/OIDC is supported
• fail early if the Node/npm trusted-publishing minimums are not met
• align checkout/setup-node/setup-bun versions with the working Api-Wrappers/tmdb-wrapper release workflow
• run the release job through the npm GitHub environment
• restrict version PR creation and npm publishing to main
• ignore .changeset/README.md when detecting pending changesets

Root cause

The failed 1.1.1 release ran Node 20.20.2 with npm 10.8.2. npm trusted publishing requires Node 22.14.0+ and npm 11.5.1+. Although the workflow had id-token: write, npm 10 could not use OIDC for registry authentication and the publish fell through to the setup-node placeholder token, producing npm's misleading scoped-package E404 response.

The package itself exists on npm and the build/test/package verification all passed before the publish step.

Validation

• matched the trusted-publishing runtime already used by Api-Wrappers/tmdb-wrapper
• retained id-token: write and the npm registry configuration
• no package version or source changes; this is release infrastructure only

After this merges, the existing @api-wrappers/igdb-wrapper@1.1.1 version is still unpublished, so the next main release run should retry that version automatically.