Simplify deployment by using Kustomize to deploy the stack

[drerik]

It would be easier to deploy the application stack if we use kustomize to deploy the stack instead of the set of commands in the make file.

It will simplify deployment when using a ci/cd pipeline for deployment, and at the same time allow users to adopt their deployment to their own cluster.

[entlein]

At the moment, we have the px deploy for the pixie deployment (which requires a token) and the make/helm for kubescape . Thus, we are using the most popular installer for each upstream project with an opinionated values/override.
In the case of pixie, kustomize is the underlying mechanism.

[entlein]

The full deployment of the soc stack will be published here soon as a Makefile using the upstream deployment methods of both kubescape (helm) and pixie(skaffold/kustomize). Once all features are in the upstream projects (and/or pre-agreed fork-only features), we will match their originally supported artefacts so keep maintenance low.
The makefile that I will publish here, will not be binding to anyone but just an example that I maintain to show users how to set the best config options.