fix(release): point the last model at v0.10.0 and stamp the real telemetry version

[msluszniak]

Description

Two version bugs found while checking the release preconditions, plus the RELEASE.md step that would have reintroduced one of them.

1. One model still pinned to the previous release. all-MiniLM-L6-v2's tokenizer resolved through VERSION_TAG (v0.9.0) while the same file is fetched from v0.10.0 by the three MiniLM model entries a few hundred lines above. It was the only such reference left, against 288 already on NEXT_VERSION_TAG. Both tags serve the file today, so nothing was broken, but it is a stray pin to a release we are moving off.

That leaves VERSION_TAG with no reader and noUnusedLocals rejects it, so it is removed until the post-release bump re-adds it. An eslint exclusion cannot help here: the error is tsc TS6133, and an underscore prefix does not exempt a module-level constant either (checked both).

2. Telemetry reported libVersion: "0.0.0" on every download event. Its TODO pointed at #1291, which is closed and about RNET_BASE_URL in clang-tidy, so the reference is gone rather than carried forward.

It stays a literal rather than an import, and the code says why: the emitted module sits under lib/module/, where a relative path to the manifest resolves to bob's {"type":"module"} stub, and a self-referencing react-native-executorch/package.json import would depend on the consuming bundler supporting package exports. A stale string is analytics noise; a failed import breaks the bundle. A unit test asserts the posted libVersion equals package.json, so a missed bump fails CI.

3. RELEASE.md step 10 was wrong. It said to leave model URLs alone after bumping the tags, because the shipped ones "now resolve through VERSION_TAG". They do not: the URLs name the constant, not the tag, so bumping NEXT_VERSION_TAG to the next minor would silently repoint all 288 models at a release that does not exist. The step now says to rewrite the shipped URLs, to re-add VERSION_TAG, and to bump LIB_VERSION.

Introduces a breaking change?

• Yes
• No

Type of change

• Bug fix (change which fixes an issue)
• New feature (change which adds functionality)
• Documentation update (improves or adds clarity to existing documentation)
• Other (chores, tests, code style improvements etc.)

Tested on

• iOS
• Android

Testing instructions

yarn workspace react-native-executorch typecheck is clean and the full suite passes: 3842 tests, 30 suites, 4 snapshots (the apiSurface snapshot is unchanged, so dropping VERSION_TAG did not alter the public surface).

Separately, every resolve/v0.10.0 URL the registry can build was probed against Hugging Face: 309 unique artifacts across 47 repos, all 200. The only non-200 was a literal ${name} from models.ts:1208, which builds voice_styles/${name}.json from a loop variable, so it is an artefact of extracting URLs statically rather than a missing file.

Checklist

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings