[Serverless][Kibana QA QG] exception_operators_date_numeric_types:essentials:qa:serverless:release tests optimization

[MadameSheema]

Context

One of the requirements for keeping the overall Security Solution tests executed as part of the Kibana QA quality is gate, is for all the tests to be executed in less than 45 min.

Currently our Kibana QA quality gate takes more than 1h to be executed.

What is happening?

The API tests executed under exception_operators_date_numeric_types:essentials:qa:serverless:release takes more than 46 minues to be executed, if on top of that, we put the time we need to setup and terminate the pipeline, that might be one of the causes why we end up having more than the expected execution time.

What we expect?

For the tests to be refactored, regrouped or parallelized in a way that take less time to be executed. It can be revisited also if all of those tests needs to be executed as part of the Kibana QA quality gate.

To take into consideration

If this ticket is not prioritized and this tasks takes time to be targeted, we'll have to disable the tests in favor of not having the whole pipeline disabled.

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/security-detection-engine (Team:Detection Engine)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[yctercero]

I think these are ok to skip in the QA pipeline - I had added them as these have been stable for years now and didn't see any harm, but they would not fall under our "must run" tests for QA pipeline.