ci: Move Gradle-only jobs to Bitrise tahoe runners

[sentry-junior]

📜 Description

Follow-up to #6226. Moves the remaining jobs that are just "build with Gradle (and maybe talk to an external service)" onto the Bitrise tahoe pool:

• integration-tests-ui.yml – Ui tests (assemble + Sauce Labs)
• integration-tests-ui-critical.yml – Build job only
• integration-tests-size.yml – SDK size analysis
• integration-tests-macrobenchmark.yml – assemble + Sauce Labs (manual dispatch)
• codeql-analysis.yml – was GitHub-hosted macos-15
• generate-javadocs.yml – runs on release
• format-code.yml – spotlessApply

The replay snapshot upload step in the Ui tests job used shopt -s globstar, which macOS's bash 3.2 doesn't support, so it now collects the PNGs with find.

Left on GitHub-hosted runners on purpose

• Emulator jobs (agp-matrix.yml, Maestro tests in integration-tests-ui-critical.yml) need KVM and an x86_64 emulator. The Bitrise pools are Apple Silicon macOS VMs, so there's no nested virtualization for the emulator.
• system-tests-backend.yml and the Spring Boot 2/3/4 matrices start a Kafka (Redpanda) container through docker in test/system-test-runner.py. The macOS VMs have no Docker.
• release-build.yml builds the artifacts that get published. I'd rather not change the host OS for release artifacts in the same PR. It can be a separate follow-up if we want it.
• Lightweight jobs (danger, validate-pr, labels, high-risk-code, tombstone check, license compliance, release, release-comment-issues, update-deps) don't need much CPU or memory, and some depend on Linux tools (for example, GNU sed -i in license compliance).

💡 Motivation and Context

The Build job has been green on tahoe since #6226 (about 10–15 min on an M4 VM). The other Gradle-heavy jobs run into the same memory pressure on ubuntu-latest and should get the same speedup.

💚 How did you test it?

• actionlint passes against the existing .github/actionlint.yaml, which already declares bitrise_pool_name:tahoe.
• This PR's CI is the real test for Ui tests, UI Tests Critical / Build, SDK Size Analysis, and Format Code.
• CodeQL (push to main/schedule), Generate Javadocs (release), and Macrobenchmark (workflow_dispatch) don't run on PRs. Their first run will happen after merge. CodeQL already ran on Apple Silicon (macos-15), so the main unknown there is the runner image.

📝 Checklist

• No breaking change or entry added to the changelog.

🔮 Next steps

• Decide whether release-build.yml should move too.
• Rename "Build Job ubuntu-latest - Java 17" together with the ruleset update (see ci: Run Build job on Bitrise tahoe runners #6226).

#skip-changelog

via no.

--

View Junior Session [Sentry]

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.60.0 (1)	release

⚙️ sentry-android Build Distribution Settings