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

[julien-deramond]

astro@5.10.0

Release note

New priority option

Astro introduces a new priority option for the <Image /> and <Picture /> components, which automatically sets the loading, decoding, and fetchpriority attributes to their optimal values for above-the-fold images which should be loaded immediately.

There's also a note from Astro:

You should only use the priority option for images that are critical to the initial rendering of the page, and ideally only one image per page. This is often an image identified as the LCP element when running Lighthouse tests. Using it for too many images will lead to performance issues, as it forces the browser to load those images immediately, potentially blocking the rendering of other content.

I won't especially apply this priority option for now. Let's see if we can find some useful use cases that could benefit from this new feature.

Responsive images feature

The responsive images feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.
The new responsive images feature in Astro automatically generates optimized images for different screen sizes and resolutions, and applies the correct attributes to ensure that images are displayed correctly on all devices.

Right now, we don't need especially this feature, except if we want to spend some time to fine-tune this aspect. Let's postpone that for whenever we'd like to spend some time on it.

Live collections vs build-time collections

This is an experimental feature, so nothing to do on our side.

rollup@4.44.0

Release note

These changes are safe to adopt as they bring potential source mapping improvements for debugging while having no negative impact on our build process.

stylelint@16.21.0

Release note

Linting jobs are passing.

terser@5.43.1

Changelog

Running npm run dist doesn't change the dist files compared to the previous version in our main branch.