Add remaining rule testing suites to cloudbeat pre-merge checks

[DaveSys911]

Motivation

Why are we doing this task? what it the value to the user.

Definition of done

Add file system, controller & kube-api, kubelet tests to pre-merge.

• Fix file system flaky tests
• split kube api tests
• Get decision regarding kubelet & controller(split,optimise,subset) or as is.

Out of scope

What is not included in this task

Related tasks/epics

Will be handled after https://github.com/elastic/security-team/issues/4049

Checklist

Please follow the following checklist in the beginning of your work, please comment with a suggested of high level solution. It should include:

• Comment describing high level implementation details
  • Include API and data models
  • Include assumptions being taken
  • Provide backward/forward compatibility when changing data model schemas and key constants
  • Mention relevant individuals with a reason (getting feedback, fyi etc)
• Submit a PR for our technical index that includes breaking changes/ new features

Before closing this ticket

• Commit the technical index PR
• Reference to tech-debts that shall be solved as we move forward

[DaveSys911]

addressed by pr #298
File system rules still need addressing.