[never-seek]

Why

The Android CI run on main failed before Gradle started because GitHub-hosted runners received a connection reset while downloading the Gradle distribution from the Tencent mirror. The CodeQL workflow already demonstrated that using Gradle's official distribution endpoint only inside GitHub Actions succeeds.

What changed

Added the same CI-only wrapper URL substitution to Android CI. Local development keeps the existing China-friendly Tencent mirror; GitHub Actions replaces only the remote host with services.gradle.org before running Gradle.

Verification

• The workflow YAML parsed successfully.
• The substitution was validated against gradle-wrapper.properties.
• The equivalent CodeQL custom Android build completed successfully on GitHub Actions.

Checklist

• I kept this PR focused and updated relevant documentation.
• I did not include cookies, credentials, Apple IDs, real aliases, signing keys, or personal logs.
• I agree to license this contribution under the repository's MIT License.