Ensure that all the new models/actions/bug fixes to our methodology implementation for 3.2 is properly stateful where necessary. As we support ability to save states, we need to ensure that there is little to no effect/difference between running the same scenario from stabilization vs loading a state from any point in the scenario. The end result of the scenario should be the same!
This MR address all the issues found with all the new additions between 3.1 and 3.2
I also added a lot of infrastrucre support to make this easier in the future to detect/diagnose/debug state issues