[BUG] github workflows have a number of issues

[bkmartinjr]

the current github compatibility workflows show several errors that need to be diagnosed/resolved:

1. All of the smoke tests (eg, run from compatibility_tests) generate an error which doesn't seem to cause a fail, but still looks wrong. I believe this is code in client/tests/globalSetup.js failing.

ProviderError: EC2 Metadata token request returned error
    at ClientRequest.<anonymous> (/home/runner/work/cellxgene/cellxgene/client/node_modules/@aws-sdk/credential-provider-imds/dist/cjs/remoteProvider/httpRequest.js:22:38)
    at ClientRequest.emit (events.js:375:28)
    at HTTPParser.parserOnIncomingClient (_http_client.js:647:27)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17)
    at Socket.socketOnData (_http_client.js:515:22)
    at Socket.emit (events.js:375:28)
    at addChunk (internal/streams/readable.js:290:12)
    at readableAddChunk (internal/streams/readable.js:265:9)
    at Socket.Readable.push (internal/streams/readable.js:204:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:188:23) {
  tryNextLink: true,
  statusCode: 400,
  '$metadata': { attempts: 1, totalRetryDelay: 0 }
}

2. the smoke-test when run in compatibility workflows seems to not clean up correctly, resulting in a failure and error message:

Jest did not exit one second after the test run has completed.

This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] e2e: `jest --config __tests__/e2e/e2eJestConfig.json e2e/e2e.test.js "--verbose" "false"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] e2e script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.