Seperate reporting for each test suite #495
Description
In quarkus-ls (which shares a similar project structure, since it extends lsp4mp), I made a change recently that reports the results from the different test suites separately. This is helpful, because the tests for the jdt component are flaky, which means we often don't check (or don't even run!) the tests for the language server component.
In quarkus-ls I accomplished with with parallel GitHub jobs. Currently we use the Eclipse Jenkins for PR CI in this repo, but we could consider only using Jenkins for releasing and using GitHub Actions to run the PR CI.
It might also be possible to do this "multiple reporting" with Jenkins, I think there are Jenkins plugins to add separate entries into the GitHub CI reporting, and we can configure the build to always run all the test suites even if the previous ones failed. This might be a good route, considering the tests tend to pass more consistently on Jenkins, likely due to the agents having more resources (CPU, memory)