fix(css): ensure order of extracted CSS

[susnux]

Description

Without this the order of the extracted CSS rules is defined by the order renderChunk of the css plugin is called. So with this the order of CSS rules is always in alphabetical order of the output chunks.

Previously on my project every time I ran the build the output style.css was different by rule order, which caused unnecessary conflicts.

[bolt-new-by-stackblitz[bot]]

Run & review this pull request in StackBlitz Codeflow.

[patak-dev]

/ecosystem-ci run

[vite-ecosystem-ci[bot]]

📝 Ran ecosystem CI on 9f584f1: Open

suite	result	latest scheduled
astro	undefined skipped	:white_check_mark: success
sveltekit	:x: failure	:x: failure
vike	:x: failure	:x: failure
vitest	:x: failure	:x: failure

:white_check_mark: analogjs, histoire, ladle, laravel, marko, nuxt, previewjs, quasar, qwik, rakkas, remix, unocss, vite-plugin-pwa, vite-plugin-react, vite-plugin-react-pages, vite-plugin-react-swc, vite-plugin-svelte, vite-plugin-vue, vite-setup-catalogue, vitepress

[susnux]

Rebased to resolve the conflict.

[bluwy]

/ecosystem-ci run

[vite-ecosystem-ci[bot]]

📝 Ran ecosystem CI on f34bc55: Open

suite	result	latest scheduled
nuxt	:x: failure	:x: failure
vite-plugin-react-pages	:x: failure	:x: failure
vitest	:x: failure	:x: failure

:white_check_mark: analogjs, astro, histoire, ladle, laravel, marko, previewjs, quasar, qwik, rakkas, remix, sveltekit, unocss, vike, vite-plugin-pwa, vite-plugin-react, vite-plugin-react-swc, vite-plugin-svelte, vite-plugin-vue, vite-setup-catalogue, vitepress