[test] Enable type-unaware versions of disabled typed-aware lint rules

[eps1lon]

Summary

Re-enable the following lint rules:

• dot-notation
• no-implied-eval
• no-throw-literal

Context

Noticed during #24810 that we have disabled some type-aware lint rules for "performance considerations". I suspect this actually refers to the required type checking not because the rules themselves are slow.

If they were in fact only disabled to avoid type-ware linting, we should enable their type-unaware counterparts. The typescript-eslint repo says these versions "don't work with typescript" but it's unclear what they mean: do these versions have false-negatives or false-positives¹? False positives would be fine since we don't expect linting to catch every error anyway. false-negatives would be more problematic but I haven't seen false-negatives yet.

¹
false-negative: error reported that isn't one
false-positive: no error reported even though it is one

[mui-pr-bot]

No bundle size changes

Generated by 🚫 dangerJS against 11874f0

[oliviertassinari]

Agree with all you said.

TIMING=1 yarn lint returns in this PR and in my env:

Rule	Time (ms)	Relative
import/no-cycle	43641.930	29.9%
mocha/no-nested-tests	10677.706	7.3%
mocha/no-identical-title	10191.786	7.0%
mocha/no-exclusive-tests	7090.581	4.9%
mocha/no-skipped-tests	6822.207	4.7%
import/extensions	3665.945	2.5%
mocha/no-pending-tests	3598.851	2.5%
mocha/no-async-describe	3582.821	2.5%
mocha/no-global-tests	3578.034	2.5%
mocha/no-top-level-hooks	3531.212	2.4%

On a related note, I wonder why eslint runs in 3mins now, when it was running in /2 the time in #21758 6 months ago. Maybe it's pickers related.