feat(api-server): TLS, mTLS support

This is not really something that we expect to be used in
production due to the prevalence of load balancers and
reverse proxies in most production scale web application
deployments, but it is a must have for testing and also
for us to be able to claim that we take the secure by
default design principle seriously.

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>

package.json

@@ -2,6 +2,7 @@
   "name": "@hyperledger-labs/cactus",
   "private": true,
   "scripts": {
+    "run-ci": "./tools/ci.sh",
     "configure": "lerna clean --yes && lerna bootstrap && npm-run-all build generate-api-server-config",
     "generate-api-server-config": "node ./tools/generate-api-server-config.js",
     "start:api-server": "node ./packages/cactus-cmd-api-server/dist/lib/main/typescript/cmd/cactus-api.js --config-file=.config.json",

packages/cactus-cmd-api-server/package.json

@@ -74,10 +74,12 @@
     "convict-format-with-validator": "6.0.0",
     "cors": "2.8.5",
     "express": "4.17.1",
+    "express-http-proxy": "1.6.0",
     "express-openapi-validator": "3.10.0",
     "joi": "14.3.1",
     "js-sha3": "0.8.0",
     "node-fetch": "3.0.0-beta.4",
+    "node-forge": "0.9.1",
     "secp256k1": "4.0.0",
     "semver": "7.3.2",
     "sha3": "2.1.2",
@@ -89,8 +91,10 @@
     "@types/convict": "5.2.1",
     "@types/cors": "2.8.6",
     "@types/express": "4.17.6",
+    "@types/express-http-proxy": "1.6.1",
     "@types/joi": "14.3.4",
     "@types/multer": "1.4.2",
+    "@types/node-forge": "0.9.3",
     "@types/secp256k1": "3.5.3",
     "@types/semver": "7.3.1",
     "@types/uuid": "7.0.2"