v2.4.1 — npm metadata refresh & contributor docs

A docs- and metadata-only patch. No code changes — same library as 2.4.0.

This release primarily makes the v2.4.0 positioning work visible on the npm registry, where most prospective users discover the package.

What's new

New description leads with "v3 score-based (invisible)" so users discovering the package via npm search immediately know it's the score-based variant (not v2 challenges or hCaptcha).
Expanded keywords: added recaptcha-v3, score-based, invisible, abort-signal, enterprise, typescript, bot-protection, ios, android, and others — improves discoverability for the actual use cases.
Declared engines.node >=18 to match the CI test matrix. Older Node runtimes will see a warning during install but installs will still complete.

README: full rewrite with clearer positioning, a "Picking the right package" table for v2/v3/Enterprise/hCaptcha, an honest "About the WebView approach" section, per-error reference table, and an FAQ comparing this package to alternatives.
CONTRIBUTING.md: rewrite — removed stale references to a monorepo, an example/ directory, and pre-commit hooks that didn't exist in the project.
SECURITY.md (new): private vulnerability reporting flow via GitHub security advisories; supported-versions table; explicit scope.

Issue templates (bug.yml, feature.yml) with structured fields and pre-flight checks that redirect "wrong package" reports before they're filed.
Pull request template with a Conventional Commits checklist.
Issue config.yml that disables blank issues and points security reports, v2 challenge seekers, and hCaptcha seekers to the right destinations.

- "@valture/react-native-recaptcha-v3": "^2.4.0"
+ "@valture/react-native-recaptcha-v3": "^2.4.1"

No source changes required. Identical runtime behavior.

If you're upgrading from a version older than 2.4.0, the meaningful changes are in the v2.4.0 release notes.

Full Changelog: v2.4.0...v2.4.1