Sys 287 jest it up

[TieDyedSheep]

This will need to be merged into dev to test the functionality. This adds jest-it-up to track coverage historically in the repo's jest config. After this is merged there are a few test cases that will be somewhat difficult to test but this is coded so that we should be able to migrate the changes without any impact to anything without an npm script for test:coverage. this will look to see if test:coverage exists and if it does it will assume the repo running CI is using jest and will use jest-it-up to store current coverage requirements.

this will use both the most recent coverage levels as well as a global variable (that can be overridden at the repo level) to determine "target coverage". The intention is to require coverage to stay the same or improve until it hits the target coverage (currently 80%) and once it hits target coverage, it just has to stay above that target.

ex: initially starts with 0% in jest config. runs and his 50%. Next run must be 50% or higher or the build will fail. Once it gets past 80% coverage could go up to 90% and drop back down to 80% and still pass the build.

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Key issues to review Script Logic The script checks for test:coverage and runs it if available, otherwise, it defaults to npm run test. However, the logic to handle the coverage results and the conditions under which the build should fail or pass might need further refinement to ensure they align with the intended workflow requirements. Coverage Thresholds The coverage thresholds are set to 0, which might not be effective for ensuring code quality. Consider setting meaningful initial thresholds to enforce a minimum coverage standard.