Fix failures in CLI

[fedinskiy]

Summary

We have --stream parameter enabled everywhere by default, but this behavior conflicts with --platform option, we use in several tests

Please select the relevant options.

• Bug fix (non-breaking change which fixes an issue)
• Dependency update
• Refactoring
• Backport
• New scenario (non-breaking change which adds functionality)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[michalvavrik]

I don't know anything about failures, but I think the PR description makes sense.

If you specify the platform BOM without version, I'd expect this to work (like RHBQ I can migrate from 3.2 to 3.8 but still want to specify group id and artifact id). But in cases that are changed by this PR, version is always added and then, it doesn't make sense to require stream.

Quarkus CLI docs is silent on that so I'll approve:

Quarkus version:
  -S, --stream=platformKey:streamId
                             A target stream, for example:
                               io.quarkus.platform:2.0
  -P, --platform-bom=groupId:artifactId:version
                             A specific Quarkus platform BOM, for example:
                               io.quarkus.platform:quarkus-bom:2.2.0.Final
                               io.quarkus::999-SNAPSHOT  2.2.0.Final
                             Default groupId: io.quarkus.platform
                             Default artifactId: quarkus-bom

Please merge it if the CI is green.