Components: Add sleep() before all Tab() to fix flaky tests

[tyxla]

What?

This PR adds some additional sleep() calls before all press.Tab() calls to fix the flakiness.

Why?

To reduce the test flakiness. Another press.Tab() test failed right during merging #58968 to trunk so I think we should apply this everywhere and see how it goes.

How?

We're adding some wait time (10ms which is the default of sleep()) before tabbing.

This doesn't really fix the root cause, but we're aiming to fix the flaky tests for now.

We also did this in #58629 and #58968.

Testing Instructions

Verify all tests pass.

Testing Instructions for Keyboard

None

Screenshots or screencast

None

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: tyxla <tyxla@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Flaky tests detected in b84ba73.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7901704414
📝 Reported issues:

• [Flaky Test] list view should correctly reflect navigation items' structure #58980 in /test/e2e/specs/editor/blocks/navigation-list-view.spec.js

[Mamaduka]

Let's give this a try.

Is there an issue for resolving the root cause of the flakiness? We should probably include reverting "hacks" like these as a follow-up step there.

[tyxla]

Is there an issue for resolving the root cause of the flakiness? We should probably include reverting "hacks" like these as a follow-up step there.

Good idea. I've opened #59071 to keep track of this.