feat: expose jiti.evalModule

[pi0]

🔗 Linked issue

#137

❓ 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

Rework of #139, great idea by @hairyf to expose internal eval function to eval any code

Co-Authored-By: Mr.Mao <951416545@qq.com>

📝 Checklist

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

[szmarczak]

Because

const x: string = 'x';

(x || {}) as Record<string, any>

compiles, it would be much safer to type it like this:

const cache = (opts.cache as ModuleCache || parentCache || {} as ModuleCache);

or even better:

const cache: ModuleCache = opts.cache || parentCache || {};

This way it would error that opts.cache does not match ModuleCache.

[pi0]

Do you mind to open a refactor PR? 👍🏼