Support for IBM Kubernetes (k8s)/OpenShift cloud

**Description**

- [ ] get documentation on IBM Cloud
- operational guide
- in general
- how to get access to a sgx-enabled VM and/or container and, for containers, what the intended deployment model is (e.g., how is kernel device passed, is container supposed to run psw or will the psw socket be shared from host, and if so how, ..)
- any scriptability options
- [ ] get access to IBM Cloud
- [ ] investigate technical approach for
- [ ] using docker images with k8s
- [ ] converting docker-compose to k8s (see, e.g., https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/)
- [ ] to run docker/docker-compose equivalents _from within a container_.
- might require shared volumes for source on `dev` container so volume mounts work
- [ ] general fabric-on-kubernetes guides (see e.g., [FAB-11240](https://jira.hyperledger.org/browse/FAB-11240) which seems
tasked to do exactly that but as-of-2020-07-07 seems still very early WIP ..)
- [ ] might also require refactoring standard chaincode to use external builder (otherwise it would expect docker to build and run the corresponding chaincode)
- [ ] implement/documentation aspects:
- [ ] Core FPC with integration tests (but not docker-compose; ie., demo only via mock)
- [ ] Full FPC support (including docker-compose and docker-compose based demo)
- [ ] fpc chaincode running scalably via k8s (in external builder, see #320). [For some related information, see, e.g., [medium article](https://medium.com/swlh/how-to-implement-hyperledger-fabric-external-chaincodes-within-a-kubernetes-cluster-fd01d7544523)
- [ ] stagging
- [ ] most bang for the buck probably would be to do chaincode-deployment to k8s via external builders while still running the infrastructure via docker(-compose) in our tests. Note: docker(-compose) use and related scripts are only for tests so doing that first without doing scalable chaincode enablement would not be thaat useful in a production environment wherreas the converse is useful.

**Link to feature or bug**

**Link to dependent issues**