feat(tools): corda AIO start/stop per node

[petermetz]

Is your feature request related to a problem? Please describe.

Currently the corda AIO image only supports shutting down and starting all the nodes at once only.
This causes race condition problems with the cordapp deployment endpoint on weaker hardware (such as the CI environment).
We need to be able to control the individual nodes' JVM processes so that we can cherry pick which nodes to start and shut down exactly when.

Describe the solution you'd like

Supervisord to have separate program directives for each party's node (A,B,C) and also one for the Notary.
Deprecate the old way of doing it which was by running the runnodes jar produced by cordform (the gradle tooling).

Describe alternatives you've considered

Considered not spending time on this, but it came back to haunt us with the Cordapp jar deployment feature so it has to be done.
Another alternative I considered was to use docker in docker and run separate containers for each corda node. This could also be a fine solution but would involve more work and end up being more complex than it needs to be since we should be able to solve the individual control of node processes by directly launching the JVM processes ourselves via supervisord.

Additional context

This campe up during the development of the Cordapp jar deployment via SSH+SCP feature (one of many).

cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo @jagpreetsinghsasan