[Threat Hunting] Integrate API tests as part of the Security Solution execution workflows

[MadameSheema]

We have seen that the Threat Hunting API tests are currently located in x-pack/test/api_integration instead of x-pack/test/security_solution_api_integration. By that, the tests are not currently executed in any serverless environment. In this ticket is described all the tasks that we need to solve the issue, also to make sure that the tests are properly integrated in all the flows we own:

Tasks

Preview Give feedback

1. [Threat Hunting] Move the API tests to the x-pack/test/security_solution_api_integration folder #181683
   Team: SecuritySolution Team:Threat Hunting Team:Threat Hunting:Explore Team:Threat Hunting:Investigations +4
   
2. [Threat Hunting] Include API tests as part of the periodic and QG pipeline #181684
   Team: SecuritySolution Team:Threat Hunting Team:Threat Hunting:Explore Team:Threat Hunting:Investigations +4
   
3. [Investigations] Green execution in periodic pipeline #181686
   Team: SecuritySolution Team:Threat Hunting Team:Threat Hunting:Investigations +3
4. [Explore] Green execution in periodic pipeline #181685
   Team: SecuritySolution Team:Threat Hunting Team:Threat Hunting:Explore +3
5. [Investigations] Add API tests to the Kibana release quality gate #181687
   Team: SecuritySolution Team:Threat Hunting Team:Threat Hunting:Investigations +3
   
6. [Explore] Add API tests to the Kibana release quality gate #181688
   Team: SecuritySolution Team:Threat Hunting Team:Threat Hunting:Explore +3

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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