Build(deps-dev): Bump the development-dependencies group with 4 updates

[julien-deramond]

@astrojs/sitemap ^3.4.0 → ^3.4.1

@astrojs/sitemap

We're not impacted by the initial issue.

---

astro ^5.8.1 → ^5.9.0

astro@5.9.0

There's no need for us to use the new Markdown renderer to content loaders, and we don't use the supportedAstroFeatures.

New experimental CSP flag experimentation

I quickly tried out the new experimental CSP flag just out of curiosity.

For instance, the generated 404.html page would be:

<   <meta name="generator" content="Astro v5.8.1">
---
>   <meta name="generator" content="Astro v5.9.0">
40a41,42
>   <meta http-equiv="content-security-policy"
>     content=" style-src 'self' 'sha256-GbquMC32s3w1n7n35GTnFvRivAu9h3ewYsKDcJSoOyw=' 'sha256-vv9IoKo7BSLbWcUHr3tNmfNVmm5L/9Cfn2H6LMk7/ow='; script-src 'self' 'sha256-uofanfzmv4RYtykfO1L3dkyOe0EWPKUgyZ2zSL3qsGw=' 'sha256-BF0290pkb3jxQsE7z00xR8Imp8X34FLC88L0lkMnrGw=' 'sha256-QzWFZi+FLIx23tnm9SBU4aEgx4x8DsuASP07mfqol/c=' 'sha256-0chmwFk0zaA528yFfGV7J9ppIpdfTPPULncDF3WG7Zs=' 'sha256-eIXWvAmxkr251LJZkjniEK5LcPF3NkapbJepohwYRIc=' 'sha256-Q2BPg90ZMplYY+FSdApNErhpWafg2hcRRbndmvxuL/Q=' 'sha256-U7a72oKuFFz8D7GUHLA1NZ0ciymHmDOc9T9aVDg2rWU=' 'sha256-p9VbHs/ClkQc+x63XdUjvCAgeWxA4ZGvpebJtMn9jbs=';">

Without modifications, this is the rendering we get while running npm run start:

So it would need more modifications if we're willing to put that in place. Postponing for when it's going to be no more experimental.

---

terser ^5.40.0 → ^5.41.0

terser@5.41.0

There's no diff between dist directories from this branch generated by npm run dist and the main branch.

---

zod ^3.25.50 → ^3.25.51

zod@3.25.51

No impact as the docs compile.