[BUG] Tracking issue for failing Cypress tests.

[Swiddis]

What is the bug?
Now that we have a running E2E action, we need to fix our Cypress tests in CI conditions. I suspect many of the failures are due to the CI environment itself not being set up correctly, lots of them may be outdated, and maybe a handful could indicate bugs that have been untested for a while. This issue is a tracking issue for fixing our tests.

• [BUG] Outdated Cypress tests in 9_integrations #1039
• [BUG][FTR] 4_panels.spec "With Security" fails to find "Test panel" in table #1278

How can one reproduce the bug?
Run the Cypress E2E action. Because the actions support manual running, you can try it on your fork directly, but they're also run nightly.

What is the expected behavior?
The tests should pass.

What is your host/environment?

• Defined in the workflow file.

Do you have any screenshots?
N/A

Do you have any additional context?
Once we fix them at home, we can look at fixing the tests in FTR.

[Swiddis]

Superseded by #1338