deps(deps): bump @astrojs/mdx from 4.3.9 to 4.3.10

[//]: # (dependabot-start)
⚠️ **Dependabot is rebasing this PR** ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

[//]: # (dependabot-end)

Bumps [@astrojs/mdx](https://github.com/withastro/astro/tree/HEAD/packages/integrations/mdx) from 4.3.9 to 4.3.10.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/withastro/astro/releases"><code>@​astrojs/mdx</code>'s releases</a>.</em></p>
<blockquote>
<h2><code>@​astrojs/mdx</code><a href="https://github.com/4"><code>@​4</code></a>.3.10</h2>
<h3>Patch Changes</h3>
<ul>
<li>
<p><a href="https://redirect.github.com/withastro/astro/pull/14715">#14715</a> <a href="https://github.com/withastro/astro/commit/3d55c5d0fb520d470b33d391e5b68861f5b51271"><code>3d55c5d</code></a> Thanks <a href="https://github.com/ascorbic"><code>@​ascorbic</code></a>! - Adds support for client hydration in <code>getContainerRenderer()</code></p>
<p>The <code>getContainerRenderer()</code> function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call <code>container.addClientRenderer()</code> with the appropriate client renderer entrypoint.</p>
<p>See <a href="https://github.com/withastro/astro/blob/main/examples/container-with-vitest/test/ReactWrapper.test.ts">the <code>container-with-vitest</code> demo</a> for a usage example, and <a href="https://docs.astro.build/en/reference/container-reference/#renderers-option">the Container API documentation</a> for more information on using framework components with the experimental Container API.</p>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/integrations/mdx/CHANGELOG.md"><code>@​astrojs/mdx</code>'s changelog</a>.</em></p>
<blockquote>
<h2>4.3.10</h2>
<h3>Patch Changes</h3>
<ul>
<li>
<p><a href="https://redirect.github.com/withastro/astro/pull/14715">#14715</a> <a href="https://github.com/withastro/astro/commit/3d55c5d0fb520d470b33d391e5b68861f5b51271"><code>3d55c5d</code></a> Thanks <a href="https://github.com/ascorbic"><code>@​ascorbic</code></a>! - Adds support for client hydration in <code>getContainerRenderer()</code></p>
<p>The <code>getContainerRenderer()</code> function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call <code>container.addClientRenderer()</code> with the appropriate client renderer entrypoint.</p>
<p>See <a href="https://github.com/withastro/astro/blob/main/examples/container-with-vitest/test/ReactWrapper.test.ts">the <code>container-with-vitest</code> demo</a> for a usage example, and <a href="https://docs.astro.build/en/reference/container-reference/#renderers-option">the Container API documentation</a> for more information on using framework components with the experimental Container API.</p>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/withastro/astro/commit/7a5f28006e9b1f6ad77c7884991ba551ca9ff35b"><code>7a5f280</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/integrations/mdx/issues/14702">#14702</a>)</li>
<li><a href="https://github.com/withastro/astro/commit/3d55c5d0fb520d470b33d391e5b68861f5b51271"><code>3d55c5d</code></a> feat: return <code>clientEntrypoint</code> from <code>getContainerRenderer</code> (<a href="https://github.com/withastro/astro/tree/HEAD/packages/integrations/mdx/issues/14715">#14715</a>)</li>
<li>See full diff in <a href="https://github.com/withastro/astro/commits/@astrojs/mdx@4.3.10/packages/integrations/mdx">compare view</a></li>
</ul>
</details>
<br />


[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)


</details>