[Fiona2016]

Problem

The stored remote configuration was matched on [proxy ?? site, applicationId, env, version], with version being the application's own version. Every app upgrade therefore discarded it. The first session after an upgrade was drawn on the init values and reported no rcVersion.

Change

• The application version is dropped from the identity. An installed app runs one version at a time, so the previous release's settings are the better answer until the new fetch is stored.
• This matches the iOS SDK.
• app_version is still sent on each request.
• Files written by earlier builds carry the old four-part identity and no longer match, so the first launch after this SDK upgrade discards the cache once and rewrites it.
• The README sentence about cache scope is updated.

Verification

• vitest run --coverage: 40 files, 1033 tests passed.
• yarn typecheck is clean.
• prettier --check src README.md is clean.
• eslint on the changed files is clean.
• New and updated tests:
  • a file written under another app version is applied, and app_version and applied_version are still sent;
  • the identity is the same whatever the app version;
  • an old-format file is ignored once.
• Negative control: with config.version back in the identity, the remote configuration spec fails.