Bubble up failure from developerPreviewUpdate

[amcaplan]

WHY are these changes introduced?

Fixes #3173

WHAT is this pull request doing?

We aren't actually refreshing the token in the background during dev, because the error wasn't bubbling up and we have a mechanism to only refresh on error:

cli/packages/app/src/cli/services/dev.ts

Lines 331 to 333 in f2e51f8

	} catch (_err) {
	try {
	await refreshToken()

We seem to use these functions in a limited number of other places, but I don't see anywhere they shouldn't cause a failure.

How to test your changes?

Run dev overnight on an app with UI extensions. You should never see a complaint that dev preview mode isn't being updated.

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]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	73.02% (+0.01% 🔼)	6253/8563
🟡	Branches	70.54% (-0.02% 🔻)	3038/4307
🟡	Functions	71.75% (+0.01% 🔼)	1585/2209
🟡	Lines	74.18% (+0.01% 🔼)	5937/8003

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / ConcurrentOutput.tsx	97.62% (-2.38% 🔻)	75% (-8.33% 🔻)	100%	97.44% (-2.56% 🔻)

Test suite run success

1483 tests passing in 669 suites.

Report generated by 🧪jest coverage report action from cc3ada0