fix: support import.meta.env and import.meta.env?.prop

[pi0]

🔗 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)
• ✨ 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

Currently, we support import.meta.env.foobar by replacing AST to process.env.foobar but using import.meta.env itself was not possible and could possibly make issues like cannot use import outside of a module.

This PR also adds support for import.meta.env? with optional chaining, increases type safety and simplifies code.

📝 Checklist

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