Don't start the dev session if there are build errors

[isaacroldan]

WHY are these changes introduced?

We don't want to even start the dev-session if any of the extensions failed to build.

WHAT is this pull request doing?

• If there are build errors, don't start the session and finish the process
• Add a new method to display errors in multiple extensions with a better UI

How to test your changes?

1. Create 2 extensions with build error (for example, change import to importa)
2. Run shopify app dev
3. Verify that:
   • Build errors are displayed with proper formatting
   • The extension handle is shown as a prefix
   • The dev session is aborted with an appropriate error message

Measuring impact

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[isaacroldan]

• Improve UI when displaying multiple errors returned from dev-update/create #5232
• Rethrow functions esbuild errors #5231
• Don't start the dev session if there are build errors #5230 👈 (View in Graphite)
• Improve dev-session retry and error report #5226
• main

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

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run "pnpm changeset add" to track your changes and include them in the next release CHANGELOG.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	75.19% (-0.07% 🔻)	8891/11825
🟡	Branches	70.42% (-0.01% 🔻)	4333/6153
🟡	Functions	75.01% (-0.1% 🔻)	2335/3113
🟡	Lines	75.75% (-0.06% 🔻)	8402/11092

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / dev-session.ts	79.31% (-6.3% 🔻)	66.67% (-0.52% 🔻)	79.49% (-9.08% 🔻)	84.8% (-6.43% 🔻)

Test suite run success

2004 tests passing in 905 suites.

Report generated by 🧪jest coverage report action from fe089c6