chore: Bump version to v0.10.0

[msluszniak]

Description

Step 9 of the minor release process: bumps main to the next development cycle now that release/0.9 has been cut. Bumps the 3 package.json versions (core, bare-resource-fetcher, expo-resource-fetcher) to 0.10.0, bumps LIB_VERSION to 0.10.0 (so VERSION_TAG resolves to resolve/v0.10.0), and bumps PREVIOUS_VERSION_TAG to resolve/v0.9.0. The two deprecated Llama 3.2 QLoRA aliases now inline their resolve/v0.8.0 pin (those files only exist at v0.8.0). RELEASE.md is updated to describe the VERSION_TAG (dev) / PREVIOUS_VERSION_TAG (latest stable) convention.

Important

Merge AFTER v0.9.0 has been tagged and published to npm. The daily nightly publish workflow runs against main, so merging earlier would cause nightlies to start tagging as 0.10.0-* before 0.9.0 is on the latest dist-tag.

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

N/A — pure version bump on main; v0.10.0 is in development, no release artifacts exist yet.

Screenshots

Related issues

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

Additional notes

The QLoRA pin previously rode on PREVIOUS_VERSION_TAG = resolve/v0.8.0; inlining it lets PREVIOUS_VERSION_TAG carry its intended "latest stable" meaning going forward.