Support for running quorum without the transaction manager

[melihbirim]

Current setup always includes at least one transactions manager. Some installation scenarios do not need a transaction manager at all and support for running GoQuourm without the transaction manager is needed.

I added a running sample 4 nodes RAFT configuration.

tubuarge@3a0d3b2

[libby]

Update rb scripts to support quorum only if the transaction manager is not set.

• qube-init calls out the below scripts, should support
  ./qube-init qubernetes-no-tm.yaml
• qubernetes
• quorum-config
• the scripts should be able to process an empty tm: field, test with a file qubernetes-no-tm.yaml which removes the tm manager field https://github.com/ConsenSys/qubernetes/blob/master/qubernetes.yaml#L36

with tm support:

  - Node_UserIdent: quorum-node1
    Key_Dir: key1
    quorum:
      quorum:
        # supported: (raft | istanbul)
        consensus: istanbul
        Quorum_Version: 2.6.0
      tm:
        # (tessera|constellation)
        Name: tessera
        Tm_Version: 0.10.4

without tm support:

  - Node_UserIdent: quorum-node1
    Key_Dir: key1
    quorum:
      quorum:
        # supported: (raft | istanbul)
        consensus: istanbul
        Quorum_Version: 2.6.0

Update k8s templates to leave out transaction manager resources if set to none.

• most importantly update deployment template to leave out the transaction manager if it is not set.
  e.g. https://github.com/ConsenSys/qubernetes/blob/master/templates/k8s/quorum-deployment.yaml.erb#L81

Update quorum templates to leave out generate Transaction Manger specific resources if not set.

Updating qctl

Modify qctl to include option for no tm manger, e.g. qctl init --tm=none

[solidnerd]

@melihbirim @libby I started to work on the generators to also support it directly in the generation. Feel free to have a look on it.