Address npm ci slowdown

[mccalluc]

• Fix Cypress has gotten much slower #2683

Cypress runs in just over 10 minutes... typical of duration before regression.
We'll need to make sure that our dev environments are up to date and in sync with these changes.

Disabled a portion of one test. If you think you understand the problem, great... otherwise I'd vote for filing an issue to sort it out later, and merge the rest of this now.

[mccalluc]

Hitting node-sass / gyp problem now.

[mccalluc]

dev-start working locally now. With any luck tests will pass, and complete in less time: The last couple commits have been more copy-and-paste from SO than I'd like.

[mccalluc]

RUN npm ci fails with peer dependency conflicts... because we don't COPY the conf file...

[mccalluc]

Cypress passes! Installs seem to work, but Node tests fail early. There's a lot of upgrading here, and maybe the behavior of something we rely on has changed?

  /home/runner/work/portal-ui/portal-ui/context/node_modules/jsdom/lib/jsdom/living/xhr/XMLHttpRequest-impl.js:111
        referrer: _ownerDocument.URL,
                                 ^
...
      at /home/runner/work/portal-ui/portal-ui/context/app/static/js/hooks/useImmediateDescendantProv.js:131:32
      at Array.map (<anonymous>)
      at _callee$ (/home/runner/work/portal-ui/portal-ui/context/app/static/js/hooks/useImmediateDescendantProv.js:126:57)
      at tryCatch (/home/runner/work/portal-ui/portal-ui/context/node_modules/regenerator-runtime/runtime.js:45:40)

potentially relevant post: https://dev.to/vnglst/did-you-forget-to-wait-something-async-in-your-test-59j7 ... Problem might be with test cleanup?

Maybe there's a way to change jest logging to see what test it had started before the error? Or assume it's the other test in that directory: context/app/static/js/components/entity-search/SearchWrapper/utils.spec.js

[john-conroy]

I can't remember; were the issues you described here the only issues blocking us from using node 16 when we pinned to 14?

[mccalluc]

My memory is that we just didn't want to take too big of a jump all at once, and the format change in package-lock.json was a little scary.