feat!: make TestEnvironment be unconstrained

[nventuro]

TestEnvironment throws a gazillion warnings due to calling oracles in constrained functions. We could have unsafe blocks, but this would be misleading since we're not constraining anything, and there'd be risk of user error. The correct call is to make these functions be unconstrained.

However, since they work with mutable references, these themselves cannot be called from constrained functions. Nor should they - this would again require unsafe blocks, but we cannot constrain these results, and we don't anyway since tests are run in a non-adversarial environment.

There should be no difference between constrained and unconstrained tests (except unconstrained tests might be a smidge faster). Therefore, the simplest and most correct way forward is to make all tests and helpers unconstrained, which is what I do here. This ends up removing a ton of 'missing unsafe' warnings.

[sklppy88]

Looks nice ! I think overall we should be more explicit on the rule which you summed up really well, which is mut references cannot cross between constrained <-> unconstrained. Imo this is obvious with context but not so obvious without, and it took me even awhile to see how this affects the code, even if I understood the reason behind it.

[AztecBot]

Docs Preview

Hey there! 👋 You can check your preview at https://66f3e0893305781a4b646c50--aztec-docs-dev.netlify.app