Allow allocators in testing (take 2)

[Argmaster]

This pull request default initializes main.stackAllocator and main.globalAllocator to testing allocator.

Resolves: #1286

[IntegratedQuantum]

Did you check if they are usable in testing?

[Argmaster]

One issue with that is that there is no difference between deallocating something with stackAllocator and globalAllocator in testing, right?
Also, is the testing allocator reset every test or just at the very end?

[IntegratedQuantum]

Yes, that is true, though that is technically also possible (to some degree) at runtime, since the stackAllocator uses the globalAllocator as a fallback. If it's trivial to fix, go for it, otherwise I'd say it's not worth the effort.

Also, is the testing allocator reset every test or just at the very end?

It leak-checks every test.

[Argmaster]

Yes, that is true, though that is technically also possible (to some degree) at runtime, since the stackAllocator uses the globalAllocator as a fallback. If it's trivial to fix, go for it, otherwise I'd say it's not worth the effort.

Hm, then its not trivial to fix I think and its not really critical tbh. IMO out of scope for this PR.

[IntegratedQuantum]

Alright, then I'm still waiting for an answer to my earlier question:

Did you check if they are usable in testing?

[Argmaster]

Did you check if they are usable in testing?

Right, I didn't push it;
I added a small test which I think should be sufficient:

test "allocators" {
	const allocation1 = stackAllocator.create(u64);
	stackAllocator.destroy(allocation1);

	const allocation2 = globalAllocator.create(u64);
	globalAllocator.destroy(allocation2);
}