Feature/manifest as crd

[cloudziu]

This PR implements partially #357 and resolves #787.
The Frontend service has been redone to instead of using secret files as Claudie manifests, now it use CRD.

group: claudie.io
version: v1beta1
kind: inputmanifest

List of changes that will change UX:

• Secret data has been offloaded from the manifest: Now the inputManifest only reference a secret resource in the provider sections.
• The secret placement isn't limited upfront by namespace, it can be created in any namespace. The same goes for InputManifest. There is no need for any additional labels on the InputManifest/Secret resource
• Because of the architecture, the validation webhook won't check the provider's section at kubectl apply level. The workflow will be similar to Kubernetes Pods scenario. If a Pod referencing a non-existing secret will be created - it will CrashLoop in an error state, Claudie will generate an error and check again in 60s. (Interval of REQUEUE_AFTER_ERROR const var).
• When deleting an InputManifest - the file won't get removed until the cluster won't be removed, because of v1beta1.claudie.io/finalizer read more

# Create a secret
apiVersion: v1
kind: Secret
metadata:
  name: hetzner-1
  namespace: any-namespace
type: Opaque
data:
  apitoken: QSBUWSBDV0FOSUFDWktVCg==
 ---
 # Create an InputManifest
apiVersion: claudie.io/v1beta1
kind: InputManifest
metadata:
  name: hetzner-test-manifest
  namespace: claudie
spec:
  providers:
      - name: hetzner-secret
        providerType: hetzner
        secretRef:
          name: hetzner-1
          namespace: any-namespace 
  nodePools:
    dynamic:
      - name: control-hetzner-1
        providerSpec:
          name: hetzner-secret
          region: nbg1
          zone: nbg1-dc3
        count: 1
        serverType: cpx11
        image: ubuntu-22.04

    . . . 

  kubernetes:
    clusters:
      - name: hetzner-test-cluster
        version: v1.30.0
        network: 192.168.2.0/24
        pools:
          control:
            - control-hetzner-1
          compute:
            - compute-hetzner-1

ToDo:

• Alter test sets, so they will utilise inputmanifest type.

[MarioUhrik]

Because of the architecture, the validation webhook won't check the provider's section at kubectl apply level. The workflow will be similar to Kubernetes Pods scenario. If a Pod referencing a non-existing secret will be created - it will CrashLoop in an error state, Claudie will generate an error and check again in 60s. (Interval of REQUEUE_AFTER_ERROR const var).

I don't like this much, but I understand this is the best way.
I wouldn't want the creation of a CRD to be blocked by the absence of the secret.
However, I think the default interval should be much shorter, no more than 5 seconds.

[MarioUhrik]

Will the status of the inputManifest be updated by events and errors?

[Despire]

Nice work thus far 👍

[cloudziu]

Will the status of the inputManifest be updated by events and errors?

Yes, the inputmanifest .status field will contain the status of the cluster (including errors) + when an error will occur an Kubernetes event will be created with the err message.

[MiroslavRepka]

Great work @cloudziu!