Containerize connector plugins

[petermetz]

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

Cloud has became the de-facto way of running applications on computers.
Containers are rapidly becoming (have become?) the de-facto way of running applications in the cloud.
We therefore need to make sure that Cactus is not just built and distributed as the language native artifacts (e.g. npm packages/webpack bundles) but that it's also distributed as containers.
This doesn't just mean containerizing the API server that can host the plugins, but also means containerizing each plugin individually as well OR providing a generic image of the API server that can be configured to run any and all of the available Cactus plugins on-demand.

Note

It is necessary to separate this issue into an issue for each ledger connector.

Describe the solution you'd like

I want to be able to whisper things like this to my terminal and expect to have a fully functional connector for Ledger X up and running in a few seconds and with the config.json file mounted at the specified path/volume that gets picked up by the API server running inside the container as well.

Fabric

echo "{ \"some-configuration\": 42 } " > config.json

docker run \
  --rm \
  --volume ./config.json:/opt/hyperledger/cactus/cactus-plugin-ledger-connector-fabric/config.json \ 
  hyperledger/cactus-plugin-ledger-connector-fabric

Besu

echo "{ \"some-configuration\": 42 } " > config.json

docker run \
  --rm \
  --volume ./config.json:/opt/hyperledger/cactus/cactus-plugin-ledger-connector-besu/config.json \ 
  hyperledger/cactus-plugin-ledger-connector-besu

Corda

echo "{ \"some-configuration\": 42 } " > config.json

docker run \
  --rm \
  --volume ./config.json:/opt/hyperledger/cactus/cactus-plugin-ledger-connector-corda/config.json \ 
  hyperledger/cactus-plugin-ledger-connector-corda

Quorum

echo "{ \"some-configuration\": 42 } " > config.json

docker run \
  --rm \
  --volume ./config.json:/opt/hyperledger/cactus/cactus-plugin-ledger-connector-quorum/config.json \ 
  hyperledger/cactus-plugin-ledger-connector-quorum

Describe alternatives you've considered

The other alternative is to have a single image that can be configured at runtime to import the connector plugins as defined by the configuration. I'm still undecided on which path is easier and more convenient for people who will deploy Cactus so willing to hear opinions in the comments section of this issue.

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