Improve dev-session retry and error report

[isaacroldan]

WHY are these changes introduced?

Improves error handling and token refresh mechanisms in the dev session flow.

WHAT is this pull request doing?

• Introduces proper error handling for authentication failures during dev sessions
• Adds retry with token refresh ONLY for dev session creation and updates mutations.
• Improves error messages for expired auth sessions
• Improves debug output formatting

How to test your changes?

1. Start a dev session and let it expire (you can intentionally put a bad token in the dev session update mutation to force an authentication error)
2. Verify that you receive a clean error

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
• Improve dev-session retry and error report #5226 👈 (View in Graphite)
• 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.25% (-0.01% 🔻)	8889/11812
🟡	Branches	70.43% (-0.02% 🔻)	4332/6151
🟡	Functions	75.1% (+0.02% 🔼)	2335/3109
🟡	Lines	75.81% (-0% 🔻)	8400/11081

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / app-event-watcher.ts	93.83% (-1.23% 🔻)	86.49% (-2.7% 🔻)	90.48%	98.61%
🟢	... / dev-session.ts	85.61% (-0.68% 🔻)	67.19% (-0.05% 🔻)	88.57% (-0.71% 🔻)	91.23% (-1.22% 🔻)
🟢	... / ConcurrentOutput.tsx	98.36% (-1.64% 🔻)	88% (-4% 🔻)	100%	98.33% (-1.67% 🔻)

Test suite run success

2004 tests passing in 905 suites.

Report generated by 🧪jest coverage report action from 3388086

[gonzaloriestra]

Not sure if I'm understanding the session handling or maybe something is not working as expected. But if I break the token, I'm getting the session expired error. Shouldn't it start the login flow?