fix(nuxt): apply more import protections for nitro runtime

[pi0]

🔗 Linked issue

one issue Baroshem/nuxt-security#335

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 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

Previously we were not fully protecting nitro runtime imports for @nuxt/kit and other nuxt-relevant imports. This PR also refactors import protection plugin rules to be maintained in one place more easily.

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[chenyuncai]

That's means we cannot use "useLogger" anymore but Consola directly.

[danielroe]

Exactly 👌 useLogger is only for nuxt config/module code, not for vue or nitro runtime code.

[fabianwohlfart]

Hi guys,
Is this why I cannot import { runCommand } from 'nuxi' anylonger?
nuxt/cli#331

I need and want to run a nuxi command server side.
How can I deal with it?