Backport quarkus CLI update support

[mocenas]

Summary

Backport of changes for quarkus CLI update tests. From PRs:

• Add extraArgs method to CLIAppManager #1241

• Add checks into QuarkusCLIUtils #1239

• Fix issues in QuarkusCLIUtils #1236

• Add CLI testing utils #1235

• Add method for creating CLI apps from existing sources #1233

• Allow running CLI in dev mode, without overwriting quarkus version #1232

• Add CLI feature to update quarkus app #1188

• Bug fix (non-breaking change which fixes an issue)

• New feature (non-breaking change which adds functionality)

• Dependency update

• Refactoring

• Release (follows conventions described in the RELEASE.md)

• 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

[michalvavrik]

CLI failures look related.

[mocenas]

CLI failures look related.

I investigated that. In the end I've disabled the test and opened an upstream issue, as this really seems like an problem in quakrus CLI in version 3.8.*. quarkusio/quarkus#42567
If steps like this doesn't work (even with upstream versions) then there is something wrong:

quarkus create app app --stream=3.2
cd app
quarkus update --stream=3.8

[rsvoboda]

Why one bulk commit and not picks of the original commits (using git cherry-pick -x __HASH__)?

btw, -x is important as you will have reference to the original commit and thus the PR for better context.

[michalvavrik]

I investigated that. In the end I've disabled the test and opened an upstream issue, as this really seems like an problem in quakrus CLI in version 3.8.*. quarkusio/quarkus#42567
If steps like this doesn't work (even with upstream versions) then there is something wrong:

makes sense

[mocenas]

Why one bulk commit and not picks of the original commits (using git cherry-pick -x __HASH__)?

btw, -x is important as you will have reference to the original commit and thus the PR for better context.

To be frank, I tried to do that way, but git cherry-pick was trolling me so hard, that I decided to go this way instead.

[mocenas]

I've also disabled the shouldUpdateApplication test which is failing for same reason - quarkusio/quarkus#42567