fix(vite): don't fail builds for virtual modules that don't support inlining

[danielroe]

🔗 Linked issue

resolves nuxt/nuxt#14855

❓ 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)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Virtual CSS files that want Nuxt inline styles need to respond to the resolved ID with the correct query flags (?inline&used). I've updated three key virtual CSS modules (see linked issue). But we shouldn't fail builds if user is using some other virtual CSS module; this PR simply makes sure we skip those virtual modules. Any CSS they inject will not be inlined.)

We could also display a warning message so users at least know this is happening and know where to raise an issue. wdyt @pi0?

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	d726328
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/631f40e93d4242000891307d

[pi0]

A warning when bailing inlining because of unsupported query seems nice idea 👍🏼 This way we can signal plugin authors to add support.