See Originally posted by @shawkins in #48212 (comment)

We currently have employed several optimization techniques and split the running of our quarkus integration tests into two ci runs. I would like to propose we instead start minimizing our usage of quarkus integration tests with a soft goal of getting back to a single ci test run.

We absolutely need coverage of our scripts - but we have removed command / option specific logic (dealing with --optimized, help, etc.) from kc.sh and kc.bat, so I think we can streamline what we're covering. I'd at least say anything that is marked as DryRun which is not specifically for exercising a script should just be a unit test. Even the help command dist test is fully unit testable.

If a test is actually starting the server and is something that is expressable in the new test framework, I would be in favor of migrating it or identifying why it can't.