chore: sync package.json version with npm registry (0.9.10)

[SanthoshCharanBolt]

Description

While verifying the OIDC/Trusted Publishing fix from #102, a test publish landed 0.9.10 on npm from an untagged, off-main commit (see #103, closed). main's package.json is still at 0.9.9.

Without this fix, the next release-triggering commit to main would run yarn release --ci, compute the next version as 0.9.10 again (already published), and fail — npm rejects republishing an existing version.

This bumps main to 0.9.10 so the next real release correctly computes 0.9.11+.

Background on why main was broken

Versions 0.9.4–0.9.9 were bumped and tagged on main via chore: release commits, but every one of those publishes failed with a 404 (npm error 404 Not Found - PUT .../@boltpay%2freact-native), because npm Trusted Publishing was never configured for this package. That's now fixed:

• Fix OIDC setup for npm publish #102 corrected the workflow (id-token: write, correct registry URL, OIDC-based auth, --provenance)
• A Trusted Publisher entry was added on npmjs.com for boltapp/bolt-react-native-sdk + main-release.yml
• Verified working end-to-end via a throwaway branch/PR ([DO NOT MERGE] Verify OIDC npm publish end-to-end #103, closed) — publish succeeded with a signed provenance attestation

Security Review

• I have considered and reviewed security implications of this PR and included the summary below.

Security Impact Summary

Version-number-only change; no application code or production behavior affected.

Reviewer choices: None.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.