fix(importGlob): warn on default import css

[bluwy]

Description

Followup to #11094

I forgot to finish the import glob warnings 😅 This should be more accurate now.

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 Commit 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.

[sapphi-red]

I think we shouldn't show a warning for import.meta.glob('./fixture-c/*.css') when the value is not used.
I saw people using this pattern to just import multiple css files.

import.meta.glob('./*.css', { eager: true })

// instead of
import './a.css'
import './b.css'
import './c.css'

[bluwy]

I've thought about that but that still technically allows them to access the default import in runtime. If import.meta.glob supports "import-only" for side-effects maybe that could allow suppressing the warning 🤔