test(QSelect): explicitly ensure elements are visible before clicking

[n05la3]

See the original issue here

The QSelect random failure is probably caused by clicking on an element when it is not yet visible. Even though cypress is supposed to check that an element is visible before clicking, sometimes due to race conditions or for some other reason, the element may be found and clicked when it is not yet visible. So "should('be.visible')" has been explicitly added to ensure tests are deterministic.

The following cypress issue and blog post describe this issue and recommend explicit visibility checks.

• Conflicting information on using .should('be.visible') before .click() cypress-io/cypress#14889
• https://www.cypress.io/blog/2020/08/17/when-can-the-test-navigate#visible-elements
• https://docs.cypress.io/guides/core-concepts/interacting-with-elements#Actionability

What kind of change does this PR introduce?

• Bugfix
• Feature
• Documentation
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes
• No

The PR fulfills these requirements:

• It's submitted to the dev branch (or v[X] branch)
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• It's been tested on a Cordova (iOS, Android) app
• It's been tested on an Electron app
• Any necessary documentation has been added or updated in the docs or explained in the PR's description.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to start a new feature discussion first and wait for approval before working on it)

Other information:

[github-actions]

UI Tests Results

   74 files  1 714 suites   2m 2s ⏱️
  504 tests   504 ✅ 0 💤 0 ❌
1 574 runs  1 574 ✅ 0 💤 0 ❌

Results for commit ff706cf.

♻️ This comment has been updated with latest results.

[IlCallo]

Merged to quick-fix QSelect tests flakyness

A follow-up PR will migrate QSelect tests to use withinSelectMenu and adapt our own .select override to automatically apply the .should('be.visible') fix whenever possible