fix(eas-cli): check if export is available before validating project

[byCedric]

Why

I parallized these two actions to make the command as fast as possible. Unfortunately, this has the side effect of conflating a prompt with a command error (as seen in the screenshot below).

This reverts the parallized action back into two stages, where they can't be mixed up.

How

• First validate if a (valid) export is available
• Then validate if the project is set up properly

Test Plan

• $ bun create expo ./test
• $ cd ./test
• $ eas deploy
  • Should not trigger the prompt in the screenshot, only the error

[github-actions]

✅ Thank you for adding the changelog entry!

[github-actions]

Size Change: +439 B (0%)

Total Size: 52.9 MB

Filename	Size	Change
./packages/eas-cli/dist/eas-linux-x64.tar.gz	52.9 MB	+439 B (0%)

_{compressed-size-action}

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 52.12%. Comparing base (dadf58f) to head (2a3e88d).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/eas-cli/src/commands/worker/deploy.ts	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2569      +/-   ##
==========================================
- Coverage   52.13%   52.12%   -0.00%     
==========================================
  Files         559      559              
  Lines       21110    21111       +1     
  Branches     4317     4317              
==========================================
  Hits        11003    11003              
- Misses       9229     9230       +1     
  Partials      878      878              

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