Restrict the use of globals in functions

[mratsim]

Ideally only the main scheduler functions accesses globals besides the metrics.

While there are plenty of articles with globals considered harmful, the main motivation here is that it makes the library much harder to test.

Scalable fuzzing and property-based testing would require independent, ideally side-effect free components that can be tested independently and in parallel.