[build-tools] resolve correct projectRootDirectory during eas build:internal

[szdziedzic]

Why

We resolve incorrect and override projectRootDirectory when running eas build:internal for GCS builds that use NoVcsClient in EAS CLI as VCS client. Adding EAS_PROJECT_ROOT env var should fix it.

How

Use EAS_PROJECT_ROOT env var if EAS_NO_VCS is used

Test Plan

Tests

[szdziedzic]

• [build-tools] resolve correct projectRootDirectory during eas build:internal #495 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[sjchmiela]

Could we always pass EAS_PROJECT_ROOT (no matter EAS_NO_VCS)? I think we can expect ctx.buildDirectory / ctx.projectTargetDirectory to always be correct?

Also, why buildDirectory in one place and projectTargetDirectory in the other?

[szdziedzic]

buildDirectory is a place where project archive is located in "standard" build process and projectTargetDirectory is the place where project archive lands after checkout is done for custom builds

[szdziedzic]

Could we always pass EAS_PROJECT_ROOT (no matter EAS_NO_VCS)? I think we can expect ctx.buildDirectory / ctx.projectTargetDirectory to always be correct?

I played it safely in case it has some unknown side effects :D