Refactor Quarkus CLI tests

[michalvavrik]

Summary

• move Quarkus CLI utils and framework-like code to this FW from TS
• merge Quarkus CLI client tests in FW because there was unnecessary repetition
• add test for listing extensions

Here is how changes in the Quarkus Test Suite are going to look: quarkus-qe/quarkus-test-suite@main...michalvavrik:quarkus-test-suite:feature/quarkus-cli-refactoring I didn't run special chars on Windows, but apart of that I tested all changes with TS (native, JVM).

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices