Is your feature request related to a problem? Please describe.
When reviewing PRs like #1093 and #1090 (review), it's important to look at the output of specific GitHub Actions.

Right now this is challenging due to the sheer number of Actions being run for each PR, largely due to the acceptance tests that are necessarily split across multiple Action to avoid runtime limitations.

There are currently 278 checks run on each PR:

Scrolling through the list to find the right Action is time consuming and error-prone if you pick the wrong one. Additionally GitHub doesn't allow you to expand the scroll window so your view of the checks is limited to about 5 at a time. There also isn't a search function to, for example, just find the unit test output if that's what you're looking for.

Proposed solution
It would be nice to organize the output of these checks in the PR view if possible. Ideally everything related to acceptance tests would be grouped together.

Describe alternatives you've considered
At a minimum the GitHub Actions should be better named to be more descriptive and allow easy scanning to find the one you're looking for.

For example, the main unit test Action is currently called "Test Package Document". From just looking at the name, it's not clear if this tests packaging the documentation (which was my original expectation), or whether it runs the tests, packages the validator into a JAR file, and generates the Javadocs (which is what it actually does).

Additional context
Add any other context or screenshots about the feature request that can help us better understand your needs.