fix(vite): extract styles for shared chunks

[danielroe]

🔗 Linked issue

• resolves missing important inline styles from components used across multiple pages #25420
• resolves On production build, CSS does not get inlined in SSR response in some cases when using defineAsyncComponent #25451
• resolves Styles defined in layout omitted from the server-rendered HTML, when Client- and Lazy component use the same package in their code #22507
• resolves islands: nested components styles are not send with the server component #24480
• resolves Styling of Regular Component Lost in Production When Nested Inside Global Server Component #25330

closes #25394

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

We weren't extracting styles for chunks without a facadeModuleId, but it's safe to do so for individual module ids. This is a PR that simply adds these additional module ids to be extracted, as long as they are Vue files (which are the ones tracked in ssr context).

📝 Checklist

• I have linked an issue or discussion.
• added tests

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[danielroe]

This is not a product of changes in the code; this is vite behaviour for adding a shared component (also on main).

[danielroe]

Seems that this PR also resolves issue in #25394 (added regression test from that PR here as well).