Add capturing support in k8s

Currently, there is no capturing support in the configuration of tracee in kubernetes (via the configmap etc).
Furthermore, would be nice to control where the captured files are written to (perhaps sent via network similar to webhook as writing the captured files to local fs would be hard to fetch).

The issue names no files or tests; start by tracing Tracee's Kubernetes configuration and current captured-file handling. Define how capture is enabled through a ConfigMap and which destinations are supported, then verify that captured output can be controlled without relying only on local filesystem access.

Written by the indexing model from the issue text.