infra(eslint): limit usage of globals in src

[ST-DDT]

Fixes #3145

• Prevent usage of features not broadly available #3145

Ban the usage of globals in our src folder.
All usages of these globals have to be marked with a eslint disable rule making them easier to spot.

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	0dab34f
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/6712b443cae7a40008c4622a
😎 Deploy Preview	https://deploy-preview-3191.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.96%. Comparing base (9014715) to head (0dab34f).
Report is 1 commits behind head on next.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #3191      +/-   ##
==========================================
- Coverage   99.97%   99.96%   -0.01%     
==========================================
  Files        2798     2798              
  Lines      227335   227335              
  Branches      958      957       -1     
==========================================
- Hits       227268   227260       -8     
- Misses         67       75       +8     

Files with missing lines	Coverage Δ
src/internal/base64.ts	30.00% <ø> (ø)
src/internal/deprecated.ts	100.00% <ø> (ø)
src/modules/helpers/eval.ts	94.69% <ø> (ø)

... and 2 files with indirect coverage changes

[xDivisionByZerox]

What happened to the original implementation where globals that are not specific to an environment were allowed?

[ST-DDT]

What happened to the original implementation where globals that are not specific to an environment were allowed?

It was never added to our source and this solution was recommended to me by members of eslint.

[ST-DDT]

Also AFAIK we don't actually want to use any additional globals anyway.