tweak jest config and usage

[thewatermethod]

Description of change

We've experienced Jest continuously timing out and/or running out of memory when trying to run unit tests.

This PR contains two configuration changes that attempt to partially address this behavior

• Add two parameters to our jest execution on the frontend. --detectOpenHandles & --forceExit. There was one example in a GitHub issue of a memory leak where strings representing transpiled files where being stored and not deleted between tests. I also added --silent to make the output a bit more readable when trying to observe logged heap usage.
• Manually call the node garbage collector after each test.

These open issues helped guide me to these solutions

• Memory Leak on ridiculously simple repo jestjs/jest#7874
• Memory Leak when running multiple test. Especially with --runInBand jestjs/jest#7311

At this point it's unclear whether this is some larger issue with our configuration, or if its an issue with certain tests, or an issue with current versions of our dependencies. Multiple attempts to diagnose the problem largely failed.

This should probably be considered a temporary, stopgap measure, and this problem should be revisited.

How to test

Issue(s)

Checklists

Every PR

• Meets issue criteria
• JIRA ticket status updated
• Code is meaningfully tested
• Meets accessibility standards (WCAG 2.1 Levels A, AA)
• API Documentation updated
• Boundary diagram updated
• Logical Data Model updated
• Architectural Decision Records written for major infrastructure decisions

Production Deploy

• Staging smoke test completed

After merge/deploy

• Update JIRA ticket status

[jasalisbury]

Can you write a ticket marked tech debt and point to this PR? It is interesting the heap size looks to be growing still in CI but no OOM.

[thewatermethod]

Created https://ocio-jira.acf.hhs.gov/browse/TTAHUB-426