feat: use public processor for txe private calls part 1

[sklppy88]

This PR is currently in draft and looking for feedback, but shows how we can use the public processor to handle state and put the TXe even closer to a real execution model. This is a purely additive change, and implements a new endpoint on the test_environment as well as a cheatcode to make a private call with this new method.

Currently when we enqueue a public function call, we execute it right away. Also, we do not run the teardown function as the final call. Also, we are forced to manually add side-effects to trees and build a block. (This is currently extremely brittle with how public side-effects are handled). With this change we will correctly run functions in order, also we are letting the processor handle all the side effect management, which cuts down on the complexity by a lot and further lets us explore using a real node to process TXe transactions.

There is one remaining outstanding issue:

• More robust note hash and nullifier management will have to be implemented, which will include cases of private function calling an external private function which emits side effects.

[sklppy88]

• feat: use public processor for txe private calls part 1 #12779 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[sklppy88]

Superceded by #14020