[eas-cli] Add eas update:embedded:upload command

[gwdp]

Why

EAS Update bundle diffing can't generate patches against the JS bundle embedded in a native build, so the first OTA after install always downloads the full bundle. This command registers the embedded bundle with EAS Update so the diff worker can use it as a patch base.

Ref ENG-21033

How

• New eas update:embedded:upload command with --platform, --bundle, --manifest, --channel, and optional --build-id / --json flags
• Uploads the bundle via presigned URL then registers it via uploadEmbeddedUpdate; two-phase spinner shows progress for each step
• Retries registration on EMBEDDED_UPDATE_ASSET_NOT_AVAILABLE (GCS finalization race) with exponential backoff; hints on other failures that the bundle may already be registered

Test Plan

• yarn jest src/commands/update/embedded/__tests__/upload.test.ts src/graphql/__tests__/client-test.ts — 24 tests pass
• yarn tsc && yarn lint pass
• Ran locally against a real iOS archive:

$ node bin/dev update:embedded:upload \
  --platform ios \
  --bundle ios/CoinFlip.xcarchive/Products/Applications/CoinFlipPreview.app/main.jsbundle \
  --manifest ios/CoinFlip.xcarchive/Products/Applications/CoinFlipPreview.app/EXUpdates.bundle/app.manifest \
  --channel production
✔ Uploaded bundle
✔ Registered ios embedded update (runtimeVersion: 1.0.0, channel: "production")
Embedded update ID: 5f2b4c4b-77a0-45cc-9320-bc8ec2eb36fb

[gwdp]

• [eas-cli] Add eas update:embedded:list command #3722
• [eas-cli] Add eas update:embedded:view command #3721
• [build-tools] Auto-upload embedded bundle after build when opt-in flag is set #3767
• [eas-cli] Add eas update:embedded:upload command #3720 👈 (View in Graphite)
• main

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

[linear]

ENG-21033

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.91%. Comparing base (fa6c877) to head (de82930).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3720      +/-   ##
==========================================
+ Coverage   56.80%   56.91%   +0.12%     
==========================================
  Files         904      908       +4     
  Lines       39112    39210      +98     
  Branches     8173     8187      +14     
==========================================
+ Hits        22214    22314     +100     
+ Misses      15428    15426       -2     
  Partials     1470     1470              

☔ View full report in Codecov by Sentry.
📢 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.

[github-actions]

Subscribed to pull request

File Patterns	Mentions
**/*	@douglowder
packages/eas-cli/src/update/**	@wschurman, @quinlanj
packages/eas-cli/src/commands/update/**	@wschurman, @quinlanj

Generated by CodeMention

[github-actions]

✅ Thank you for adding the changelog entry!

[quinlanj]

use fs-extra so you can await instead

[quinlanj]

This code will run on any error that is not an EmbeddedUpdateAssetNotAvailableError, so it wouldn't make sense to print this since we don't know if the issue is bundleregistration (ie) network error, etc.

Also I'm not sure i follow the use case here, if the bundle is already registered (the embedded asset) wouldn't the creation of the embedded update succeed? Or if you meant the EmbeddedUpdateEntity already exists, we can detect that from www and throw a special error to catch that specific case (so we aren't telling users to delete manually when we catch a generic error)

[quinlanj]

use fs-extra so we can await