use vscode-elements natively

[pelikhan]

Don't go through older react layer/

---

- ✨ Refactored `PromptType` to include a `PromptTemplateId`.
- 🔄 Updated `PromptFormatPromptTemplateRequestDTO` to use `PromptTemplateId` instead of `PromptId`.
- 🔧 Removed unused imports from various files.
- 👌 Replaced direct references in the public API with `PromptTemplateId` for better compatibility and maintainability.

This summary captures the essence of the changes made, focusing on the structural updates that impact the user-facing part of the codebase.

AI-generated content by pr-describe may be incorrect

[github-actions]

LGTM 🚀 🎉 The pull request introduces necessary updates to handle web components in React. The TypeScript definitions for the custom elements are properly set up, and the type safety is maintained without adding significant complexity.

Here’s a brief summary of the key changes:

• Content Security Policy (CSP) Updates: Ensured that CSP headers are correctly configured.
• Markdown Preview: Updated styling for markdown previews to be more consistent with standard Markdown rendering.
• Web Components Integration: Added TypeScript support and React integration for web components, enhancing the modularity and reusability of the UI components.

These changes are well-thought-out and will improve the reliability and maintainability of the codebase. Minor adjustments could always be made later as needed.

Summary:

• CSP Updates: Addressed potential security concerns related to content inclusion.
• Markdown Styling: Improved consistency in how markdown is rendered across the platform.
• Web Components for React: Enhanced UI component design and maintainability by integrating TypeScript definitions. 🚀

The pull request looks good to go!

AI-generated content by pr-review may be incorrect