[Security Solution] Adds more cypress tests on serverless for investigations team

[MadameSheema]

Update

With the newest tests added + newest changes in main looks like we need to increase as well the number of nodes to avoid timeouts in CI.

As currently we are extremely close to arrive to achieve the parity between ESS and serverless tests, we are increasing the parallelism number to match the one we currently have for specific investigations executions in ESS.

Summary

In this PR we are making the following changes regarding the tests living in x-pack/test/security_solution_cypress/cypress/e2e/investigations regarding their execution on the first quality gate for serverless:

• Unskips alerts_charts.cy.ts
• Unskips bulk_add_to_timeline.cy.ts
• Unskips several tests inside timelines/creation.cy.ts
• Unskips several tests inside timelines/pagination.cy.ts
• Adds a reference to ticket with the reason why the tests are skipped in timelines/unsaved_timeline.cy.ts

Note that the unskipped tests have been executed several times and are passing consistently :)

Also, the tests that were marked before with .skip remain skipped in both executions.

[elasticmachine]

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 69f0540

Failed CI Steps

• Defend Workflows Cypress Tests on Serverless #2

Metrics [docs]

✅ unchanged

History

• 💔 Build #169892 failed d9c1b9a
• 💛 Build #169721 was flaky 1eee2d2
• 💛 Build #169492 was flaky 74f1965
• 💔 Build #169445 failed 058045e

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @MadameSheema

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.11	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 169379

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 169379 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 169379 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 169379 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 169379 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 169379 locally

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 169379 locally