Gracefully handle system errors while updating a draft extension

[gonzaloriestra]

WHY are these changes introduced?

When the CLI gets a 500 error while updating a draft, it's crashing in a bad way:

WHAT is this pull request doing?

Catch any error and print them properly without stopping the dev session:

How to test your changes?

Run p shopify app dev against Partners and very quickly update an extension many times until you get an error, or break the json of a locale

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

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

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	78.01% (+0.01% 🔼)	12466/15980
🟡	Branches	72.15% (+0% 🔼)	6038/8369
🟡	Functions	78.28%	3272/4180
🟡	Lines	78.44% (+0.01% 🔼)	11794/15035

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟡	... / update-extension.ts	72.34% (-0.16% 🔻)	50% (-8.33% 🔻)	60%	76.19% (-0.95% 🔻)

Test suite run success

2866 tests passing in 1253 suites.

Report generated by 🧪jest coverage report action from 12c0857

[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.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.