[build-tools] Resolve job environment after metadata update

[sjchmiela]

Summary

Stacked on #3900. Refreshes derived EAS build environment variables after GitHub-triggered job information and metadata are resolved, instead of patching Android Gradle execution directly.

I want to unify runGradleCommand and I noticed that only one of them polyfills the EAS_ environment variables for GitHub builds.

Details

• Adds a shared getResolvedJobInformationEnv helper in @expo/build-tools for profile, commit hash, username, and platform version env vars.
• Calls that helper from both BuildContext.updateJobInformation and CustomBuildContext.updateJobInformation so traditional and custom/steps builds see the resolved env.
• Reuses the helper from the worker initial build env construction to keep the mapping consistent.
• Removes the Gradle-only Android version env fallback.

Validation

CI should pass.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.03%. Comparing base (5c24631) to head (6b8a4dd).

Additional details and impacted files

@@                            Coverage Diff                            @@
##           stanley/update-env-overrides-existing    #3899      +/-   ##
=========================================================================
+ Coverage                                  59.02%   59.03%   +0.02%     
=========================================================================
  Files                                        935      935              
  Lines                                      40946    40947       +1     
  Branches                                    8624     8620       -4     
=========================================================================
+ Hits                                       24165    24171       +6     
+ Misses                                     16686    16681       -5     
  Partials                                      95       95              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR centralizes the mapping of “resolved job information” into EAS_BUILD_* environment variables and ensures both traditional and custom/steps builds receive the same resolved values after GitHub-triggered job metadata is updated, removing the Android Gradle-specific fallback.

Changes:

• Introduces getResolvedJobInformationEnv(job, metadata) in @expo/build-tools and reuses it across worker env construction and build context job updates.
• Updates both BuildContext.updateJobInformation and CustomBuildContext.updateJobInformation to apply the resolved env mapping.
• Removes the Gradle-only Android version env override logic and adds/updates tests to cover the new behavior.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/worker/src/env.ts	Uses the shared resolver to populate EAS_BUILD_* envs during initial worker env construction.
packages/build-tools/src/index.ts	Re-exports getResolvedJobInformationEnv from the package entrypoint.
packages/build-tools/src/customBuildContext.ts	Updates custom build env after job/metadata resolution using the shared resolver.
packages/build-tools/src/context.ts	Adds the shared resolver and applies it after updateJobInformation.
packages/build-tools/src/android/gradle.ts	Removes Gradle-only Android version env fallback now that envs are refreshed centrally.
packages/build-tools/src/tests/customBuildContext.test.ts	Adds coverage to ensure custom context env is updated after resolved job information is applied.
packages/build-tools/src/tests/context.test.ts	Adds coverage to ensure BuildContext env is updated after resolved job information is applied.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sjchmiela]

Fixing in #3901

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.

[github-actions]

⏩ The changelog entry check has been skipped since the "no changelog" label is present.