Make accessing unknown globals a side-effect

[lukastaegert]

This PR contains:

• bugfix
• feature
• refactor
• documentation
• other

Are tests included?

• yes (bugfixes and features will not be merged without tests)
• no

Breaking Changes?

• yes (breaking changes will not be merged unless absolutely necessary)
• no

List any relevant issue numbers:
Resolves #3045

Description

This will make accessing unknown global variables a side-effect so that unchecked variable accesses are not removed by tree-shaking. To avoid too many false positives, the global handling was revised to use a common table for existing globals as well as pure global functions. The plan is to extend this in the future to add return types to global functions as well as handle global functions that have no side-effect except calling their arguments. In the end, I hope to merge this at some point with the existing logic for builtin prototypes.

The known globals have been mostly taken from the builtin section of https://github.com/sindresorhus/globals. Additionally, this also adds the global object to global detection as either globalThis, window, global or self. I know that in any real environment, only globalThis is kind of a standard, but maybe this is a good compromise for the start.

It also adds an new treeshake.unknownGlobalSideEffects option to deactivate this.

[codecov]

Codecov Report

Merging #3068 into master will increase coverage by 0.14%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3068      +/-   ##
==========================================
+ Coverage   89.06%   89.21%   +0.14%     
==========================================
  Files         165      165              
  Lines        5715     5719       +4     
  Branches     1738     1737       -1     
==========================================
+ Hits         5090     5102      +12     
+ Misses        383      380       -3     
+ Partials      242      237       -5

Impacted Files	Coverage Δ
src/Graph.ts	92.94% <ø> (ø)	⬆️
src/ast/nodes/shared/knownGlobals.ts	100% <100%> (ø)
src/Module.ts	94.27% <100%> (+0.01%)	⬆️
src/ast/nodes/Identifier.ts	100% <100%> (+14.28%)	⬆️
src/ast/nodes/shared/FunctionNode.ts	100% <100%> (ø)	⬆️
src/ast/variables/GlobalVariable.ts	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bba1466...eec0138. Read the comment docs.

[Conduitry]

This seems to be causing this issue. Would it make sense to not assume typeof some_unknown_global has side effects? Maybe this doesn't actually make sense as a solution to the problem, I don't know. Probably disregard this. I'm still confused.

[Conduitry]

Figured out what I meant, and opened #3115.