If dev github... fails, don't fail the schema fetch command

[shauns]

WHY are these changes introduced?

Internally, we use dev github... to pull in some schema files. If this fails, don't fail the underlying command (usually dev up) -- the developer can continue to work regardless.

WHAT is this pull request doing?

exit code 0 if the error is specifically from using dev

How to test your changes?

Run dev up

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
• I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

[github-actions]

Thanks for your contribution!

Depending on what you are working on, you may want to request a review from a Shopify team:

• Themes: @shopify/advanced-edits
• UI extensions: @shopify/ui-extensions-cli
  • Checkout UI extensions: @shopify/checkout-ui-extensions-api-stewardship
• Hydrogen: @shopify/hydrogen
• Other: @shopify/app-management

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	72.58% (+0.01% 🔼)	7451/10266
🟡	Branches	69.14% (+0.02% 🔼)	3656/5288
🟡	Functions	71.57%	1969/2751
🟡	Lines	72.92% (+0.01% 🔼)	7037/9650

Test suite run success

1713 tests passing in 794 suites.

Report generated by 🧪jest coverage report action from 3027198

[mathiusj]

works in my spin:

[mathiusj]

and when running pnpm graphql-codegen:get-graphql-schemas: