[codex] Set up release-please

[devakone]

Summary

• Adds CI validation for the root npm package.
• Adds a separate publish-npm.yml workflow modeled after ng-open-cv.
• Moves release-please config to .github/release-please-config.json.
• Bootstraps the release manifest at the current package version 1.0.0.
• Publishes to npm via Trusted Publishing/OIDC when release-please creates a GitHub release.

Branch change

• Created origin/main from master.
• Switched the repository default branch from master to main.
• Retargeted PR fix: modernize react i18next compatibility #13 to main.

Trusted Publishing

• Uses the same high-level flow as ng-open-cv: validate PRs, run release-please only on pushes to main, publish only when release_created == true.
• Uses id-token: write, Node 22.14.0, npm 11.5.1, and npm publish --provenance --access public.
• Does not use NPM_TOKEN.
• npm package settings need the trusted publisher entry for devakone/react-i18next-helpers, workflow filename publish-npm.yml, allowed action npm publish, unless it already exists.

Validation

• Parsed .github/release-please-config.json and .release-please-manifest.json with Node.
• Parsed all .github/workflows/*.yml files with Ruby YAML.
• Ran git diff --check.
• Ran npm run prepublishOnly; passed, then reverted generated dist churn to keep this PR scoped.
• Ran npm pack --dry-run; passed.

Notes

• origin/master was left in place as a compatibility branch.
• This repo publishes from the package root; unlike ng-open-cv, there is no Angular dist/<package> publish directory.