make jcstress default targets enabled:

- I do not see the aarch64 failures as adoptium see
- there is weird oscilation of NUMBER of tests between windows, ppc64le, aarch64 and x86_64
- That is folowed by time oscialtions (http://****:8080/search/?q=-B1t2%253A+jcstress)
- windows aprox 11 hours (all on vagrant)
- tests 3534, test cases 42408 tests in all variants
- quite a few soft (api mishmash) errors
- aarch64 1-3days, avarage in 1.2 days (depending on HW)
- tests 3534, test cases 168840 tests in all variants
- ppc64le 1-3days, avarage in 1.5 days (depending on HW)
- tests 3534, test cases 168840 tests in all variants
- x86_64 1-3days, avarage in 2 days (depending on HW)
- tests 3534, test cases 84420 tests in all variants
- (on linuxes, the 84420 x 168840 seesm to be oscilating, probably due to some CPU setup, obviously it is making the jumping the time from x->x*2->(x*2)/2...)
- I had locally implemented conversion of jcstress resutls to junit.xml
- this must be usptreamed (together with 5more issues I found in meantime:
* [CODETOOLS-7903818 jcstress do not print structuralised results](https://bugs.openjdk.org/browse/CODETOOLS-7903818)
* [CODETOOLS-7903754](https://bugs.openjdk.org/browse/CODETOOLS-7903754) [jcstress should die asap - with report - on broken jvm/hw, instead of waiting on kill](https://bugs.openjdk.org/browse/CODETOOLS-7903754)
* [CODETOOLS-7903774](https://bugs.openjdk.org/browse/CODETOOLS-7903774) [make all tests combinations printing nicer and/or configurable](https://bugs.openjdk.org/browse/CODETOOLS-7903774)
* [CODETOOLS-7903766](https://bugs.openjdk.org/browse/CODETOOLS-7903766) [affinity detected but later marked as invalid argument](https://bugs.openjdk.org/browse/CODETOOLS-7903766)
* [CODETOOLS-7903750](https://bugs.openjdk.org/browse/CODETOOLS-7903750) [TimeBudget (-tb) does not fulfill its promisses](https://bugs.openjdk.org/browse/CODETOOLS-7903750)

Thougts?

The issue discusses jcstress target durations, test-count oscillations, and upstreaming result conversion, but it names no repository files, tests, or entry points. First identify where jcstress targets and result reporting are configured, then determine the intended default targets and measurable completion criteria with the linked CODETOOLS issues.

Written by the indexing model from the issue text.