fix(ci): npm config delete proxy #656

Potentially fixing #656. Definitely improves the situation but it
is impossible to tell in advance if this will make all the other-
wise non-reproducible issues go away. Fingers crossed.

An attempt to fix the mysterious error in the CI
that can be seen at the bottom.

Based off of the advice of a fellow internet user as seen here:
https://stackoverflow.com/a/61789467

No idea if this will fix the particular error that we
are trying to fix or not, but we have to try. The
underlying issue seems to be a bug in npm itself,
but knowing that doesn't disappear the need to
find a workaround so here we go...

Error logs and link:
----------------------------

Link: https://github.com/hyperledger/cactus/runs/2179881505?check_suite_focus=true#step:5:8

Logs:

Run npm ci
  npm ci
  shell: /usr/bin/bash -e {0}
  env:
    JAVA_HOME_8.0.275_x64: /opt/hostedtoolcache/jdk/8.0.275/x64
    JAVA_HOME: /opt/hostedtoolcache/jdk/8.0.275/x64
    JAVA_HOME_8_0_275_X64: /opt/hostedtoolcache/jdk/8.0.275/x64
npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>

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

.github/workflows/ci.yml

@@ -56,6 +56,11 @@ jobs:
 
     - uses: actions/checkout@v2.3.4
 
+    # https://stackoverflow.com/a/61789467
+    - run: npm config list
+    - run: npm config delete proxy
+    - run: npm config delete http-proxy
+    - run: npm config delete https-proxy
     - run: npm ci
     - run: ./node_modules/.bin/lerna bootstrap
     - run: npm run build:dev:backend