[Security Solution] Restructure API integration tests based on their required license type

[xcrzx]

Summary

Currently, the integration tests in the Security Solution are divided into two groups based on the license type:

• x-pack/test/detection_engine_api_integration/basic - These tests are executed against a Kibana set-up with the Basic license.
• x-pack/test/detection_engine_api_integration/security_and_spaces - These tests are executed against a Kibana set-up with the trial (Platinum) license.

• Most of the tests are included in the security_and_spaces group, but some tests are also copied to the basic group. There is no clear distinction between the two groups, so developers generally add tests to the second group by default.

To improve the organization of the tests, we need to take the following actions:

• [ ] Remove any duplicate tests.
• [ ] Move any features not requiring a Platinum license to the basic group (which should be the case for most Security Solution features).
• [ ] For features that require a Platinum license, we should test that they are not accessible with the basic license in the basic group, and we should test that they work correctly in the security_and_spaces group.

For reference, features by license: https://www.elastic.co/subscriptions

### Detection Engine
- [ ] https://github.com/elastic/kibana/pull/179211
- [ ] https://github.com/elastic/kibana/pull/179706
- [ ] Rule execution folder
- [ ] Exceptions and value lists
- [ ] Rule actions folder

### Rule Management

[elasticmachine]

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

[elasticmachine]

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