[Security Solution] Specific Cypress executions for Detection Engine team

[MadameSheema]

Addresses: #153661

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 Detection Engine 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 a specific folder for the detection engine team
• We are creating 2 different executions (jus exceptions and all the the tests inside the detection engine except the exceptions one) 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-detections-response (Team:Detections and Resp)

[elasticmachine]

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

[yctercero]

LGTM - thanks so much for these updates.

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: bf924a0

Failed CI Steps

• FTR Configs #55

Metrics [docs]

✅ unchanged

History

• 💛 Build #181206 was flaky c022877
• 💚 Build #181172 succeeded 3493df1
• 💔 Build #181170 failed d41a2ba
• 💔 Build #181166 failed 79d7f5b
• 💔 Build #180589 failed 798903b
• 💔 Build #180540 failed fce4b17

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

cc @MadameSheema