feat(linter) eslint: no-new-wrappers

[alakhpc]

Part of: #479

docs: https://eslint.org/docs/latest/rules/no-new-wrappers

I am unsure of what do do with 2 of the eslint tests that use languageOptions: { globals: { String: "off" } } and /* global Boolean:off */.

I've commented them out as of now.

[codspeed-hq]

CodSpeed Performance Report

Merging #2413 will improve performances by 13.2%

_{Comparing alakhpc:eslint-no-new-wrappers (5e7f55d) with main (28ba28f)}

Summary

⚡ 7 improvements
✅ 20 untouched benchmarks

Benchmarks breakdown

	Benchmark	main	alakhpc:eslint-no-new-wrappers	Change
⚡	semantic[antd.js]	818.9 ms	756 ms	+8.32%
⚡	semantic[cal.com.tsx]	299.1 ms	289.9 ms	+3.16%
⚡	semantic[checker.ts]	636.5 ms	562.3 ms	+13.2%
⚡	semantic[pdf.mjs]	151.3 ms	146.3 ms	+3.43%
⚡	transformer[antd.js]	1.6 s	1.5 s	+3.92%
⚡	transformer[checker.ts]	1,052.4 ms	975.8 ms	+7.85%
⚡	transformer[pdf.mjs]	284 ms	274.4 ms	+3.47%

[camc314]

is this the same as https://github.com/oxc-project/oxc/blob/main/crates/oxc_linter/src/rules/unicorn/new_for_builtins.rs

or very similar?

should we merge the two rules.

Thoughts @Boshen ?

[alakhpc]

That one does seem a lot more comprehensive and should be preferred.

The only reason I can see to include this, is that this falls under correctness while new_for_builtins falls under pedantic

[Boshen]

I think we can accept this rule into correctness if we change the help text to indicate why this is correctness.

Who's got the time to read that wall of eslint rule explanation page :thrug:

[Boshen]

I changed this to pedantic to be consistent with eslint.