fix(dashboard): bundle Monaco editor with inline workers to fix CORS

[koushik717]

Re-applies #4247 with a fix for the production CORS failure that caused the revert in #4478.

Root cause of the revert

The original PR used Vite's ?worker suffix, which emits each worker as a separate JS chunk fetched by URL at runtime. In production environments where assets are served with strict CORS headers, those cross-origin worker URL fetches are blocked by the browser, breaking JSON schema autocomplete.

What changed

Switched ?worker to ?worker&inline in monaco-environment.ts:

// before
import editorWorker from 'monaco-editor/esm/vs/editor/editor.worker?worker';
import jsonWorker from 'monaco-editor/esm/vs/language/json/json.worker?worker';

// after
import editorWorker from 'monaco-editor/esm/vs/editor/editor.worker?worker&inline';
import jsonWorker from 'monaco-editor/esm/vs/language/json/json.worker?worker&inline';

?worker&inline bundles each worker as a base64 blob URL inside the main chunk. No cross-origin fetch occurs at runtime, so CORS headers on the asset server are irrelevant.

Everything else is unchanged from the original PR.

Testing

• pnpm run typecheck - same pre-existing codegen errors as main, no new errors
• Verified no separate worker chunk files are emitted (workers are inlined)
• The trade-off: slightly larger main bundle vs. no CORS dependency

---

AI disclosure (per AI_POLICY.md): I used an AI coding assistant for parts of this change and reviewed/tested everything above myself before opening this PR.

[vercel]

@koushik717 is attempting to deploy a commit to the Hatchet Team on Vercel.

A member of the Team first needs to authorize it.