[Security Solution] Switch cypress and api integration test data from es archive to programmatically generated in certain files

[dplumlee]

Related to #116374

In some of the Security Solution Rules cypress and API integration tests, we rely on es archive data that has been timestamped years ago and just extend the rule look back time to cover the time period. This isn't a reliable practice and while the 50,000 hours value we often use should cover our current test data, there are tests and use cases that can't have a look back time hardcoded.

We should look into a different approach of generating data to create a more realistic testing environment and not have to worry about tests breaking because some arbitrary time has passed

This would also allow us to unskip and update the tests skipped in the linked PR. More detail about the specific tests is listed in its summary

[elasticmachine]

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

[dplumlee]

I added API integration tests to this ticket as they have a similar issue. No tests were skipped in the linked PR but the inability to have generated data is causing shortages in testing coverage for the same reason as the cypress tests. Namely that we can't rely upon a hardcoded timestamp to retrieve data. Whatever tool we build and integrate to address this should be able to be used in both testing suites

[elasticmachine]

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

[marshallmain]

Superseded by #126389