chore(infra/biome): enable noGlobalEval

[shulaoda]

Summary

Related to #7182

I don't know if this is the right thing to do. Why use eval? Is there any special situation?

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for rspack canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	6500a39
🔍 Latest deploy log	https://app.netlify.com/sites/rspack/deploys/66c4519dd7f8990008b164db

[shulaoda]

@SoonIter cc

[SoonIter]

const dynamicImport = (specifier) => eval(import(${specifier}))
or const dynamicImport = new Function('specifier', 'return import(specifier)');`

https://github.com/TypeStrong/ts-node/blob/ddb05ef23be92a90c3ecac5a0220435c65ebbd2a/src/test/resolver.spec.ts#L76-L81

it is a trick to avoid tsc transform the dynamic import

[SoonIter]

it is a trick to avoid tsc transform the dynamic import

Sorry, this code is moved from the webpack and should be used to be compatible with node8.

this trick can be used in two cases:

1. avoid import from being transformed by tsc toPromise.resolve().then(() => require('foo'))
2. node8

[SoonIter]

You can check the dist. If the import in dist is not transformed by tsc, it can be merged.

[shulaoda]

@SoonIter same

[SoonIter]

LGTM ：D