chore(cli): skip starting dev server in exports

[EvanBacon]

Why

With static rendering we changed the CLI to start a dev server so we could ping it for resources. This prevents us from running tests in parallel and dilutes error handling as we have to parse them back from server requests.

This PR forks part of the metro dev server .bundle request into Expo CLI so we can call it directly for SSR instead of going through the dev server. We then skip starting the dev server in order to prevent using any ports.

We have to leave some of the legacy SSR code in place to support the error boundary (pending rework).

In the future we can consolidate more by removing all metro export interface code in favor of this code path, but we don't need to do that in this PR.

How

• Consolidate export code from SPA-styled exports and SSR imports.
• Remove all SSR error translation code since we now throw errors directly in-process.
• Remove all port freeing code since export no longer starts a server.e

Test Plan

Test coverage for this is very high, hopefully tests run a bit faster now.

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).

[socket-security]

No dependency changes detected. Learn more about Socket for GitHub ↗︎

👍 No dependency changes detected in pull request

[byCedric]

For reference, this PR shows why we need to skip the server in exports #28605