fix(android): track Fastlane Gemfile.lock to fix android-deploy

[TaprootFreak]

Problem

The android-deploy lane (Release workflow, Upload to Play Store step) fails with:

bundler: failed to load command: fastlane
multi_json is not part of the bundle. Add it to your Gemfile. (Gem::LoadError)
  …representable-3.2.0/lib/representable/json.rb:1
  …google-apis-core-0.18.0/.../json_representation.rb:15
  …fastlane-2.235.0/.../create_app_on_managed_play_store.rb:1

Root cause

android/ had no committed Gemfile.lock (the global *.lock rule in .gitignore covers it, and unlike ios/ it was never tracked). So bundle install resolved gems fresh on every run — a non-reproducible build.

The previous release (v1.0.85) passed with the same Gemfile; the next run's fresh resolution pulled fastlane 2.235.0, whose google-apis → representable/json load path requires multi_json, which was no longer in the resolved bundle → LoadError before upload.

ios-deploy stayed green because ios/Gemfile.lock is committed (pins fastlane 2.232.2 + multi_json 1.19.1).

Fix

1. Commit android/Gemfile.lock seeded from the proven ios/Gemfile.lock (the two Gemfiles are otherwise identical), giving a known-good graph: fastlane 2.232.2, multi_json 1.19.1.
2. Add .gitignore negations (!android/Gemfile.lock, !ios/Gemfile.lock) so the lockfiles stay tracked despite the global *.lock rule, with a self-documenting comment.
3. Pin fastlane to 2.232.2 in android/Gemfile (lock DEPENDENCIES synced to fastlane (= 2.232.2)). The android runner is ubuntu-latest and the lock carries arm64-darwin + ruby platforms; the non-frozen bundle install adds the linux platform at runtime. The exact pin guarantees no resolution path can re-select the broken 2.235.0 — multi_json 1.19.1 stays required transitively via googleauth/signet.

Note: after step 3 the android lock is no longer byte-identical to ios — the DEPENDENCIES line differs intentionally (= 2.232.2 vs ios >= 2.220). The resolved gem specs are identical.

Validation

• Reviewed via the 3-subagent workflow: Quality/Compliance + Logic reviewers both PASS_CLEAN on the final diff.
• No Dart code changed → Analyze & Test / Visual Regression / Coverage gates unaffected (path-filtered, skip on this PR).
• Final proof is the android-deploy run once this reaches the release lane (local modern-bundler validation was not possible in this environment).

Test plan

• CI green on this PR (staging gates)
• After promotion to a release tag: android-deploy loads fastlane 2.232.2 and reaches the upload step