panic when party is not part of shared config #574
Description
When a node starts and initializes from a config block, that node needs to verify:
- The party ID of the node exists in the shared config
- The signing (identity) certificate in local config is the same as in the shared config
If this is the case, the node should panic.
In case of NAT Host and port in local config may differ from the shared config
Update the integration tests that does party remove to verify that all nodes of a removed party do not start (see #543).
Should it soft stop? (maybe in the long term, not now. I general it could start and remain in soft stopped state.)