tests: increase HiveCluster assert timeouts

[dervoeti]

Description

Sometimes it takes longer than 10 minutes to create a HiveCluster in our weekly tests. I found test runs where for some reason the listener Pod on a node took a long time to start, which in turn blocked the Hive pods from starting. Mostly this succeeds shortly after the current timeout of 10 minutes, so I increased the timeout to 15 minutes.

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Author

• Changes are OpenShift compatible
• CRD changes approved
• CRD documentation for all fields, following the style guide.
• Helm chart can be installed and deployed operator works
• Integration tests passed (for non trivial changes)
• Changes need to be "offline" compatible
• Links to generated (nightly) docs added
• Release note snippet added

Reviewer

• Code contains useful comments
• Code contains useful logging statements
• (Integration-)Test cases added
• Documentation added or updated. Follows the style guide.
• Changelog updated
• Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

• Feature Tracker has been updated
• Proper release label has been added
• Links to generated (nightly) docs added
• Release note snippet added
• Add type/deprecation label & add to the deprecation schedule
• Add type/experimental label & add to the experimental features tracker

[NickLarsenNZ]

LGTM

[NickLarsenNZ]

I found test runs where for some reason the listener Pod on a node took a long time to start

I do wonder though, shouldn't the operators be installed before the tests begin?
Maybe we need to add a check to the run_test script (or build it into stackablectl).