Fix AssetSearchBar E2E tests

[somebody1234]

Pull Request Description

• Fix assetSearchBar GUI test failure #11368
  • Split "tags" E2E test into two tests to avoid timeout
• Fix https://github.com/enso-org/cloud-v2/issues/1551
  • Fix other flaky E2E tests

Important Notes

None

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.
• ~~If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
  or the Snowflake database integration, a run of the Extra Tests has been scheduled.
  • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.~~

[MrFlashAccount]

Increasing the timeout significantly affects the test pass time (if we have a failing test, we'll have to wait for 60_000 * 5 retries instead of 30_000 * 5 retries before test fail (2.5 minutes longer for each fail!). This will also affect the DX because if the test fails, we have to wait longer to see the result (each iteration becomes much slower). Do we really need that?

[somebody1234]

yeah i think it does, i'm not a fan of it either but it's certainly causing some flakiness... perhaps we should only raise the timeout on CI? because i magine CI has slower machines - personally i've never (or rarely) experienced timeouts on my local machine - and CI machines shouldn't have timeouts because (ideally) you're supposed to run the E2E tests locally before push