improve e2e tests with retry and exponential fallback #77
Description
We run the e2e tests daily via the aio-e2e-tests repo. The connection to IMS sometimes fails because we can't exchange a jwt token, and we should be using aio-lib-core-networking to do a retry with fallback.
Test failures:
FAIL e2e/e2e.js
✓ init test (4ms)
✓ getAccessToken (224ms)
✕ exchangeJwtToken (196ms)
✕ getTokenData (1ms)
✕ getOrganizations (1ms)
at Function.module.exports.sync (/home/runner/work/aio-e2e-tests/aio-e2e-tests/node_modules/execa/index.js:187:17)
at runOne (/home/runner/work/aio-e2e-tests/aio-e2e-tests/src/run.js:71:9)
at /home/runner/work/aio-e2e-tests/aio-e2e-tests/src/run.js:132:9
at Array.forEach (<anonymous>)
at runAll (/home/runner/work/aio-e2e-tests/aio-e2e-tests/src/run.js:126:29)
at processTicksAndRejections (internal/process/task_queues.js:95:5) {
command: 'npm run e2e',
exitCode: 1,
exitCodeName: 'EPERM',
stdout: '\n' +
'> @adobe/aio-lib-ims@4.2.2 e2e /home/runner/work/aio-e2e-tests/aio-e2e-tests/.repos/aio-lib-ims\n' +
'> jest --config e2e/jest.config.js\n',
stderr: undefined,
failed: true,
timedOut: false,
isCanceled: false,
killed: false,
signal: undefined
}