Formalize smart contract instance level config for domains

[peterbroadhurst]

Need to move the configuration for who submits to smart contract level configuration, which means we need to init Domain contract instance each time it is loaded into memory by the sequencer.

Two architecturally significant configurations

How is the coordinator chosen

1. Statically configured in the configuration of the contract
2. Picked dynamically between the set of endorsers
3. The sender of the transaction

How is the submitter chosen

1. Coordinator submit
2. Sender submit
3. 3rd party submission - not yet implemented

Combinations we will implement immediately

• 1+1 - core option set for Noto
• 2+1 - core option set for Pente
• 3+2 - core option set for Zeto