[Security Solution] Specific Cypress executions for AI Assistant

[MadameSheema]

Summary

This PR is part of the effort we are making to have our cypres serverless tests ready for the second quality gate (QA environment - real serverless project and also part of the initial effort started by #153664.

With the introduced changes, we are creating specific AI Assistant Cypress executions for both ESS and serverless with the aim of:

• To help to identify quickly the ownership of the tests in case of failure.
• To help to raise specific flakiness inside the tests of the team.

In this PR:

• We are creating different executions for ESS, serverless and the quality gate
• We are integrating everything with buildkite and also adding the new executions to the flaky test suite runner
• We are updating the readme
• We are updating the codeowners file to be aligned with the new changes

[elasticmachine]

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

[cavokz]

my 2c

[charlie-pichette]

Looks good. 👍🏼

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 47204fc

Failed CI Steps

• Explore - Security Solution Cypress Tests #4

Test Failures

• [job] [logs] Explore - Security Solution Cypress Tests #4 / url state sets and reads the url state for timeline by id sets and reads the url state for timeline by id

Metrics [docs]

✅ unchanged

History

• 💔 Build #181822 failed b2caeb2

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

cc @MadameSheema