feat: integrate Monaco Editor workers for enhanced code editing support

[Soulter]

fixes: #5587

Modifications / 改动点

• This is NOT a breaking change. / 这不是一个破坏性变更。

Screenshots or Test Results / 运行截图或测试结果

---

Checklist / 检查清单

• 😊 If there are new features added in the PR, I have discussed it with the authors through issues/emails, etc.
  / 如果 PR 中有新加入的功能，已经通过 Issue / 邮件等方式和作者讨论过。

• 👀 My changes have been well-tested, and "Verification Steps" and "Screenshots" have been provided above.
  / 我的更改经过了良好的测试，并已在上方提供了“验证步骤”和“运行截图”。

• 🤓 I have ensured that no new dependencies are introduced, OR if new dependencies are introduced, they have been added to the appropriate locations in requirements.txt and pyproject.toml.
  / 我确保没有引入新依赖库，或者引入了新依赖库的同时将其添加到 requirements.txt 和 pyproject.toml 文件相应位置。

• 😮 My changes do not introduce malicious code.
  / 我的更改没有引入恶意代码。

Summary by Sourcery

Enhancements:

• Update Monaco editor loader configuration to rely on the imported monaco instance rather than a remote CDN path.

[sourcery-ai]

Hey - I've left some high level feedback:

• Switching loader.config from an explicit CDN paths.vs entry to loader.config({ monaco }) makes the Monaco source location implicit; consider adding a short comment or centralizing the Monaco configuration so future changes to bundler/asset paths don’t silently break the editor.
• If monaco is imported or initialized elsewhere, it might be safer to guard this configuration with a runtime check (e.g., verifying monaco is defined and has the expected shape) to avoid hard-to-trace failures when the dashboard bootstraps in unexpected environments.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Switching `loader.config` from an explicit CDN `paths.vs` entry to `loader.config({ monaco })` makes the Monaco source location implicit; consider adding a short comment or centralizing the Monaco configuration so future changes to bundler/asset paths don’t silently break the editor.
- If `monaco` is imported or initialized elsewhere, it might be safer to guard this configuration with a runtime check (e.g., verifying `monaco` is defined and has the expected shape) to avoid hard-to-trace failures when the dashboard bootstraps in unexpected environments.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request transitions the Monaco Editor configuration from a CDN-based approach to a local bundle using dedicated web workers for various languages. The review feedback highlights that the current static import of the 'monaco-editor' library will significantly increase the initial bundle size and recommends using dynamic imports to optimize application load performance.

[gemini-code-assist]

Importing monaco-editor statically in the main entry file will cause the entire library (which is several megabytes) to be bundled into the initial chunk. This significantly increases the application's initial load time. It is recommended to remove this static import and use a dynamic import instead.

[gemini-code-assist]

To optimize performance, use a dynamic import for the Monaco Editor. This allows Vite to split the library into a separate chunk that is only loaded when needed. The @guolao/vue-monaco-editor loader handles Promises passed to the monaco property correctly.

Suggested change

	loader.config({ monaco })
	loader.config({ monaco: import('monaco-editor') })