Add the caldera test cases to the e2e tests

[shivaccuknox]

trafficstars

Currently, the caldera tests are true e2e tests since they test if the policy applied to security engine is actually doing what is intended.

We can use put this testing functionality into the current e2e tests

[shivaccuknox]

For the coco-workload e2e test, we need KVM on the runner.

This post (https://github.blog/changelog/2023-02-23-hardware-accelerated-android-virtualization-on-actions-windows-and-linux-larger-hosted-runners/) mentions that kvm is available on large runners.

From (https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners) "if you are on the GitHub Team or GitHub Enterprise Cloud plan, you can provision a runner with more cores, or a runner that's powered by a GPU or ARM processor. These machines are referred to as "larger runner." "

The SE-RAN is neither an GitHub paid team nor a GitHub Enterprise

[nandhued]

@VedRatan Can you link the draft PR?

[nandhued]

Blocked as an epf runner is yet to be in place.