Simulation setup improvements

[ValarDragon]

What is the purpose of the change

A long standing issue of the simulator is how complex / verbose its setup code is, for very little reason.
I was working on adding property checks, and got derailed in trying to simplify the setup code & be able to use the simulation manager within the executor.

One spin off is: #2587

This has some of the basic property check struct definitions in here, so that these aren't living in stale branches. Its not in use with this.

Overarching instantiation changes:

• Split up Simulator configs
• Make simulator take in a AppConstructor rather than the app itself
• (Corollaries of that):
  • Make simulation.App interface have SimulationManager method
  • Make AppStateFn take in simulation manager
  • make simulator return LastCommitId
  • Change ModuleAccountAddrs to not be defined on the app struct (ts already stateless)

Brief Changelog

• Change app.ModuleAccountAddrs -> ModuleAccountAddrs() (not driveby, needed for the
• Split up simulator config into multiple internal configs
• Change simulation setup args, to remove some of the complexity
• Move app instantiation complexity to have simulator-unique components set by the simulator rather than instantiation
• Move Action setup for gamm into the simulation package now that its more complex (driveby change)

Testing and Verifying

Simulator still works

Documentation and Release Note

• Does this pull request introduce a new feature or user-facing behavior changes? go API breaks
• Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? yes
• How is the feature or change documented? not applicable

[ValarDragon]

This todo should just get handled with more property check work, and being able to set this to 0

[czarcas7ic]

Awesome! ACK everything except for the pubsub stuff, which I know is still getting fleshed out 🚀