feature(k8s): policy k8s compatible

[josedonizetti]

1. Explain what the PR does

Fix #3322

This PR is changing policies to be compatible with Kubernetes. So a user will be able to use the same policy on the filesystem and also as a future Kubernetes CRD.

Before the policy was:

name: dig
description: traces dns events from the dig binary
scope: 
  - binary=/usr/bin/dig
rules:
  - event: net_packet_dns_request        
  - event: net_packet_dns_response

After this PR it will be:

apiVersion: aquasecurity.github.io/v1beta1
kind: TraceePolicy
metadata:
  name: dig
  annotations:
    description: traces dns events from the dig binary
spec:
  scope: 
    - binary=/usr/bin/dig
  rules:
    - event: net_packet_dns_request        
    - event: net_packet_dns_response

This PR also makes policies versioned, so if can be backward compatible if we decide to extend/change it later.
I also made descriptions non mandatory, as we don't have description under metadata, due to a future CRD implementation, and annotations are not required in kubernetes.

2. Explain how to test it

Try one of the examples policies.

3. Other comments

This PR will break the CNDR e2e tests, so if I'll be creating a PR to fix the tests prior to merging this if approved.

[yanivagman]

LGTM

[yanivagman]

Not directly related to this PR but we should consider enforcing policy names without spaces (which may cause parsing issues when listed in the event output), and maybe also limit its size

[josedonizetti]

I created an issue to keep track of it #3333