CI | Test for trustee deployment

[Xynnn007]

Now the release of kata and trustee/gc side is logically

1. kata helps to test trustee deployment and functionality with a previous rev
2. when the rev is ok, trustee cut the release with an old rev

This makes sense for a time, but it will cause issue like #1355

The most reason behind this, is that trustee now does not have its own ci suites to test the deployments and thus hard to say "ready" when publish releases.

This issue propose to resolve this step by step

1. After we get helm chart into the ecosystem, start to use kind or something to make a kubernetes e2e CI to test the deployment of trustee
2. We need at least TDX/SNP/non-TEE runner. But at first, non-TEE can be enough.
3. This e2e ci can be a new flag that tells us if the release is ready. Then we can start to publish our own releases, without relying on kata side ci.

cc @fitzthum @mythi @amd-aliem @hgowda-amd

[fitzthum]

Totally agree. Although, I wouldn't say that we entirely rely on the Kata CI today. We are only testing the k8s deployment there, which we don't document on the website. The docker compose stuff is just tested in our local CI. The operator is another flow entirely. Ofc we only have TEE hw in the Kata CI (mostly), but hopefully we're doing some manual testing of hw-specific features at development time.

Anyway, we should definitely try to get TEE hw, improve the existing e2e tests, and eliminate gaps in the coverage.