fix(storybook): update stories to support mdx2

web/.storybook/stories-category-doc-pages/examples/BasicInfrastructureExamples.stories.mdx

@@ -1,5 +1,5 @@
 import { Mermaid } from 'mdx-mermaid/Mermaid';
-import { Canvas, Meta, Story, Description } from '@storybook/addon-docs';
+import { Canvas, Meta, Story } from '@storybook/addon-docs';
 
 <Meta
   title="owncast/Documentation/Infrastructure Examples/Basic Example"
@@ -9,12 +9,9 @@ import { Canvas, Meta, Story, Description } from '@storybook/addon-docs';
   }}
 />
 
-<Description
-  markdown={`
 ## Basic
 
 This is the most basic Owncast setup and is what you get when you run it without any additional services.
-`} />
 
 <Mermaid
   chart={`graph TD
@@ -34,13 +31,10 @@ This is the most basic Owncast setup and is what you get when you run it without
 `}
 />
 
-<Description
-  markdown={`
 ## S3 Object Storage
 
 If you would like no video traffic to take place from your Owncast server to your clients, you can use S3 Object Storage to be responsible for this instead.
 Instead of video players pulling the stream from your Owncast server it would instead make these requests to a S3 provider, and Owncast would upload video to this provider to make it available.
-`} />
 
 <Mermaid
   chart={`graph TD
@@ -74,15 +68,11 @@ Instead of video players pulling the stream from your Owncast server it would in
 `}
 />
 
-<Description
-  markdown={`
 ## CDN in front of S3 Object Storage
 
 If you're using a S3 provider but would like to increase the speed of your video delivery to your clients around the world, you can use a CDN in front of your S3 provider.
 This leads to not only your server not serving any video traffic, but the video traffic would be distributed globally so each client player would be pulling video from somewhere geographically closer, reducing the likelihood of buffering and slower network requests.
 
-`} />
-
 <Mermaid
   chart={`flowchart TD
     subgraph Video Assets
@@ -119,12 +109,9 @@ This leads to not only your server not serving any video traffic, but the video
 `}
 />
 
-<Description
-  markdown={`
 ## CDN in front of Owncast
 
 If you're ok with some video requests coming directly to your Owncast server, and want to generally increase the overall speed that your viewers globally access all your Owncast assets, including video and the web interface, you can put a CDN in front of your entire Owncast server.
-`} />
 
 <Mermaid
   chart={`flowchart TD

web/.storybook/stories-category-doc-pages/examples/CDN+S3InfrastructureExamples.stories.mdx

@@ -1,5 +1,5 @@
 import { Mermaid } from 'mdx-mermaid/Mermaid';
-import { Canvas, Meta, Story, Description } from '@storybook/addon-docs';
+import { Canvas, Meta, Story } from '@storybook/addon-docs';
 
 <Meta
   title="owncast/Documentation/Infrastructure Examples/S3 With CDN Example"
@@ -9,15 +9,11 @@ import { Canvas, Meta, Story, Description } from '@storybook/addon-docs';
   }}
 />
 
-<Description
-  markdown={`
 ## CDN in front of S3 Object Storage
 
 If you're using a S3 provider but would like to increase the speed of your video delivery to your clients around the world, you can use a CDN in front of your S3 provider.
 This leads to not only your server not serving any video traffic, but the video traffic would be distributed globally so each client player would be pulling video from somewhere geographically closer, reducing the likelihood of buffering and slower network requests.
 
-`} />
-
 <Mermaid
   chart={`flowchart TD
     subgraph Video Assets

web/.storybook/stories-category-doc-pages/examples/CDNInfrastructureExamples.stories.mdx

@@ -1,5 +1,5 @@
 import { Mermaid } from 'mdx-mermaid/Mermaid';
-import { Canvas, Meta, Story, Description } from '@storybook/addon-docs';
+import { Canvas, Meta, Story } from '@storybook/addon-docs';
 
 <Meta
   title="owncast/Documentation/Infrastructure Examples/CDN Example"
@@ -9,12 +9,9 @@ import { Canvas, Meta, Story, Description } from '@storybook/addon-docs';
   }}
 />
 
-<Description
-  markdown={`
 ## CDN in front of Owncast
 
 If you're ok with some video requests coming directly to your Owncast server, and want to generally increase the overall speed that your viewers globally access all your Owncast assets, including video and the web interface, you can put a CDN in front of your entire Owncast server.
-`} />
 
 <Mermaid
   chart={`flowchart TD

web/.storybook/stories-category-doc-pages/examples/S3InfrastructureExamples.stories.mdx

@@ -1,5 +1,5 @@
 import { Mermaid } from 'mdx-mermaid/Mermaid';
-import { Canvas, Meta, Story, Description } from '@storybook/addon-docs';
+import { Canvas, Meta, Story } from '@storybook/addon-docs';
 
 <Meta
   title="owncast/Documentation/Infrastructure Examples/S3 Example"
@@ -9,13 +9,10 @@ import { Canvas, Meta, Story, Description } from '@storybook/addon-docs';
   }}
 />
 
-<Description
-  markdown={`
 ## S3 Object Storage
 
 If you would like no video traffic to take place from your Owncast server to your clients, you can use S3 Object Storage to be responsible for this instead.
 Instead of video players pulling the stream from your Owncast server it would instead make these requests to a S3 provider, and Owncast would upload video to this provider to make it available.
-`} />
 
 <Mermaid
   chart={`graph TD