[Security Solution] [FTR Test] Remove @skipInQA Tags from Tests

[WafaaNasr]

Summary

Several tests currently have the unskipInQA tag applied to them. These tags were originally added to skip tests when running in the QA/MKI environment due to missing some user privileges, once the user gets fixed on the MKI env we need to enable these tests again

Related PRs/Tests

• [Security Solution][Exceptions][API testing] Add skipInQA tag and applied for failing tests #169646
  
• [Security Solution][API testing] Move and restructures action groups in the new api integration test folder #169234
• [Security Solution][API testing] Move and restructures Risk Engine tests #170530
• [Security Solution][API testing] Move and restructures Rule execution logic #170765
• [Security Solution][API testing] Move and restructures Telemetry logic #171159
• [Detections Response][FTR] Move remaining basic license FTRs to new folder #172132

[elasticmachine]

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

[rylnd]

@WafaaNasr is this still applicable? We have a lot of tests that aren't running due to this tag.

[WafaaNasr]

@rylnd Yes, this skipInQA tag is responsible for skipping solely the failing tests on the QA/MKI environment until they are addressed either by us or the Appex QA team.

We have a lot of tests that aren't running due to this tag.

Are you referring to the QA environment? If so, please go ahead and remove this tag if you discover that the mentioned tests have been resolved on the QA environment.

Here we track these tests so that we can address them later.