fix: configure MonacoEnvironment.getWorkerUrl to prevent worker 404 fallback

[li-lizhe]

Problem

Fixes #39340

Monaco Editor's Web Worker always fails to load because MonacoEnvironment.getWorkerUrl is not configured. Without it, Monaco appends the worker label as a URL fragment (workerMain.js#editorWorkerService), which browsers encode to %23, causing a 404. The worker falls back to the main thread every time.

Solution

Add self.MonacoEnvironment.getWorkerUrl configuration that returns the worker URL without the #label fragment. The worker name is preserved via the name parameter of new Worker().

Changes

File: web/app/components/workflow/nodes/_base/components/editor/code-editor/index.tsx

Before:

if (typeof window !== 'undefined')
  loader.config({ paths: { vs: `${window.location.origin}${basePath}/vs` } })

After:

if (typeof window !== 'undefined') {
  loader.config({ paths: { vs: `${window.location.origin}${basePath}/vs` } })

  // Configure worker URL to prevent the worker label from being appended as a URL fragment.
  // Without this, Monaco generates URLs like workerMain.js#editorWorkerService, which browsers
  // encode to %23, causing a 404 and forcing the worker to fall back to the main thread.
  self.MonacoEnvironment = {
    getWorkerUrl: () => `${window.location.origin}${basePath}/vs/base/worker/workerMain.js`,
  }
}

Testing

• Verified workerMain.js loads successfully (304, 2ms) without %23 encoding
• Verified worker types: editorWorkerService and json both affected
• No breaking changes - getWorkerUrl is the standard Monaco Editor configuration

Impact

• Eliminates unnecessary 404 responses (~350KB each, 100-700ms latency)
• Worker runs in a dedicated thread instead of main thread
• Reduces server load from SSR-rendered 404 pages

[li-lizhe]

@iamjoel @zxhlyh Could you please review this PR when you have time?