Added CPU cores calculation for determining the number of concurrency workers

[birtony]

Issue This PR Addresses

Fixes #2120

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

Added CPU calculation to optimize concurrency setup for jest tests for our CI and Release workflows.

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[humphd]

This is a good change, and I think we should do it, but it didn't affect overall build times at all (i.e., compare these runs to previous runs without the change). I had hoped it might make a difference.

[chrispinkney]

Comparing this PRs checks to another PRs checks is funny. In some places it does better, in some places it does worse. Weird.

[birtony]

@chrispinkney @humphd yeah, I've had the same controversial results with testing the different number of workers for npm test, npm run jest-watch and npm run jest-update. The modifications proposed in the article @humphd found earlier did not improve the speed, but even made it worse in some cases on my machine...