feat(node:console): polyfill `node:console` module

[jculvey]

🔗 Linked issue

❓ 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)
• [x] ✨ 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

Adds a polyfill for the node:console module.

📝 Checklist

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

[IgorMinar]

LGTM! I'm guessing that we'll need to squash this PR before/during merging. But I'm not quite sure what's the norm in this repo.

[pi0]

I'm guessing that we'll need to squash this PR before/during mergin

Across unjs repos, squash is default :)

[pi0]

Few suggestions:

• We can cache const _console = globalThis.console once in top to reduce bundle impact little bit
• For various console log methods such as info, debug, .. we can redirect them to console.log in minimum runtimes rather than throwing error
• I would use explicit no-op instead of not-implemented throws for informational things such as groupStart. They won't be really needed but if a library uses them, it breaks runtime unnecessarily and they are only for formatting

[pi0]

Thanks!