feat: Add kubernetes targets

[AtzeDeVries]

This will add Kubernetes targets.

Features:

• Auto detect helm charts and guess environments from file names. This means that kustomize is not supported.
• Diff will be done against the main branch and not on the current status in ArgoCD. ArgoCD is not a requirement for the workflow anymore. Diffs will be posted as github comments
• Adds a bunch of feature related to github
  • Create comments
  • Hide comments
  • Annotate logs in actions with a level (error, warn, debug, notice)
  • Create logs groups in github actions

Note: Kyverno will be added in a later stage.

Demo PR: https://github.com/coopnorge/helloworld/pull/3285

Some screenshots

[alfredosa]

From a first pass it looks good.

Target -> run -> runInDocker -> runLocal... I am curious if that can be abstracted

But it looks okay. I think it would be best to split it into smaller targets tho but I'm okay to move if you want.

I also see that there is a core focus on e2e but I don't see a lot of unit testing to ensure behavior

[bendiknesbo]

I have not reviewed the usage of Kubeconform or Kubescore

[AtzeDeVries]

From a first pass it looks good.

Target -> run -> runInDocker -> runLocal... I am curious if that can be abstracted

But it looks okay. I think it would be best to split it into smaller targets tho but I'm okay to move if you want.

I also see that there is a core focus on e2e but I don't see a lot of unit testing to ensure behavior

The .Run/other funcs' could be abstracted in someway but they are all a bit different to best support the requirements of a tool.

The e2e is now a bit less and more focused on unit tests. Moving all devtools and it configurations (like lint config etc) under devtools allows better unit testing.

We should check if we can do testing on the targets in a way that we make sure all targets and its depenencies are run (preferable in a 'dryrun' like mode.

[alfredosa]

lgtm after enhancements (and issue opened)

Invalidated by push of 5b47d37