Global `evalContext` as a `Zone` value

[TekExplorer]

the evalContext being a global variable makes sense in some ways, but it feels like its possible fragile or buggy when used with async gaps - surely the context changed by then?

By my understanding, Zone straight up fixes this, as it provides a "scoped global" sort of value that works with async code - seeing as its from dart:async

It especially feels like thats what we'd want since we have effect, computed, etc, which can provide zone values with ease.

Other globals can probably gain similar benefit.

Is there any reason this wouldn't work better?