chore: Parallelize Tests

[rahulsom]

This will use all available cores to run tests, and parallelize by all - suite/class/method. On machines with multiple cores, this will vastly improve test performance. These times are on my M1 MBP with 10 (8P + 2E) cores. They were reported by maven on running mvn verify.

I first ran mvn verify and ignored the time.
Then I ran it thrice without this change, and thrice with this change.

All times in seconds.

	Run 1	Run 2	Run 3	Average
Before	304	306	307	306
After	120	123	118	120
Savings				186
%				61

Your checklist for this pull request

• Make sure you are requesting to pull a topic/feature/bugfix branch (right side) and not your master branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or in Jenkins JIRA
• Link to relevant pull requests, esp. upstream and downstream changes
• Did you provide a test-case? That demonstrates feature works or fixes the issue.

[lifeofguenter]

Oh wow, very cool - thanks @rahulsom !

[jtnord]

this hard codes the values which are not suitable for all environments - the values can previously be opt into this when it is run.

For example on a 3 year old laptop with and i7-10875H this will use 16 threads and surefire is set to use 756MB per fork so 12GB can be needed with this change.

this can be performed locally already with mvn -DforkCount=1c when running, and actually removes the ability to set a forkCOunt for the environment (e.g. if you have large CPU count but not the associated memory)

[lifeofguenter]

@jtnord thanks for the comment.

This can be removed once buildPlugin has support for this option.