docs: replace VitePress :::key directives with GitHub-style alerts

[Aniket-lodh]

Overview

Replace all VitePress-specific :::key container directives (:::warning, :::tip, :::info, :::danger, :::details) with GitHub-compatible alternatives across all documentation .md files.

Changes:

• :::warning → > [!WARNING]
• :::tip → > [!TIP]
• :::info → > [!NOTE]
• :::danger → > [!CAUTION]
• :::details — converting to HTML <details> breaks VitePress builds because Vue's template compiler parses JSX/HTML inside code fences as real elements.

These render correctly on both GitHub's markdown preview and VitePress 1.5+ (GitHub-flavored alerts).

Related Issue

This PR closes #2334

[netlify]

✅ Deploy Preview for creative-fairy-df92c4 ready!

Name	Link
🔨 Latest commit	74879d6
🔍 Latest deploy log	https://app.netlify.com/projects/creative-fairy-df92c4/deploys/69fc12652179e10008ab0204
😎 Deploy Preview	https://deploy-preview-2336--creative-fairy-df92c4.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[smashedr]

Just a quick heads up, you can't have text on the same line as the annotation type [!TYPE]. Example:

> [!TIP] Need to lookup the full import path of an API?
> Open up your project's `.wxt/types/imports-module.d.ts` file.

[!TIP] Need to lookup the full import path of an API?
Open up your project's .wxt/types/imports-module.d.ts file.

---

That won't render on GitHub, they all need to be split like this:

> [!TIP]  
> Need to lookup the full import path of an API?
> Open up your project's `.wxt/types/imports-module.d.ts` file.

Tip

Need to lookup the full import path of an API?
Open up your project's .wxt/types/imports-module.d.ts file.

[PatrykKuniczak]

Fix also :::code-group and :::details across all files.
And also <<< @/../packages/browser/src/index.mjs#snippet doesn't work let's fix it also there.

Let's use search in IDE and look for ::: then let's fix ALL of that.

And take a look on files before you'll push your changes.

[PatrykKuniczak]

why, IDE on save?