chore(mobile): bump versions for release + restore Node in Android CI

[raymondjacobson]

Summary

Two changes needed to actually publish a release on main:

1. Version bump for the binary build jobs to fire again. The mobile-version-check job compares packages/mobile/package.json version between HEAD and HEAD^. Once 1.5.180 landed (PR chore(mobile): resolve react-native to 0.79.5 in lockfile + pods #14365 / commit 51cf0b2eb5), every subsequent commit reported version_changed=false, so the iOS RC, Android RC, iOS Production, and Android Production jobs all got skipped. Bumps:

   • packages/mobile/package.json: 1.5.180 → 1.5.181
   • packages/mobile/ios/AudiusReactNative/Info.plist CFBundleShortVersionString: 1.1.193 → 1.1.194
   • packages/mobile/android/app/build.gradle versionName: 1.1.529 → 1.1.530

2. Android RC + Android Production CI no longer falls back to Node 22. In run 26246576840, both Android jobs failed npm ci with:

   npm error code EBADENGINE
   npm error notsup Required: {"node":">=24.10.0","npm":">=11.10.0"}
   npm error notsup Actual:   {"npm":"10.9.8","node":"v22.22.3"}
   

   The job order is Setup Node.js → Setup Android SDK → Free disk space → Setup Java (after disk cleanup) → … → Install dependencies. The "Free disk space" step does sudo rm -rf "$AGENT_TOOLSDIRECTORY", which is where actions/setup-node@v4 placed Node 24 — so by the time npm ci runs, only the runner's system Node 22 is on PATH. Java is intentionally re-set-up after cleanup; Node was not. This PR adds a matching Setup Node.js (after disk cleanup) step (plus the npm 11 upgrade) in both Android jobs.

The iOS failures in that run were caused by an unrelated duplicate make import in ContestScreen.tsx, which has already been fixed on main by 802487bb3a.

Test plan

• Merge → Mobile CI/CD on main fires all four binary build/upload jobs (version_changed=true)
• iOS RC build & upload succeeds end-to-end
• Android RC build & upload reaches `fastlane releaseCandidate` (Node 24 visible in install step logs)
• iOS Production + Android Production gated on environment approval as usual

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: c87d7df

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR