fix(build): invalidate chunk hash when css changed

[bluwy]

Description

fix #9583

Use Rollup's augmentChunkHash hook to ensure hash takes account of chunk.viteMetadata.importedCss

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the PR Title Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[patak-dev]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
astro	✅ success
histoire	✅ success
iles	✅ success
ladle	✅ success
laravel	✅ success
marko	✅ success
nuxt-framework	✅ success
previewjs	✅ success
rakkas	✅ success
sveltekit	✅ success
vite-plugin-ssr	✅ success
vite-plugin-react	✅ success
vite-plugin-react-swc	✅ success
vite-plugin-svelte	✅ success
vite-plugin-vue	✅ success
vite-setup-catalogue	✅ success
vitepress	✅ success
vitest	❌ failure
windicss	✅ success

[bluwy]

Looks like there's this TypeError: Cannot read properties of undefined (reading 'importedCss') error in Vitest. I'm not sure how that happens since we always add the metadata to all chunks in the metadata plugin, but I added an optional chain anyways to workaround the issue for now.

[patak-dev]

/ecosystem-ci run vitest

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
vitest	✅ success

[tessro]

Thank you!! ❤️