feat: add support to multiple schemas and the new KFDDistribution schema

[alessiodionisi]

Closes #96.

Based on example/new-schema-version branch

[nutellinoit]

Some little changes

[nutellinoit]

We should also change the behaviour with the certManager setting in the ingress module

Instead of

        nginx:
          # the tls section defines how the tls for the ingresses should be managed
          tls:
            # provider can be certManager, secret
            provider: certManager
        certManager:
          # the configuration for the clusterIssuer that will be created
          clusterIssuer:
            # the name of the clusterIssuer
            name: letsencrypt-fury
            # the email used during issuing procedures
            email: example@sighup.io
            # the type of the clusterIssuer, can be only http01, dns01 integration is not yet supported
            type: http01

We should swap type with solvers to make the user free to define the configuration

        nginx:
          # the tls section defines how the tls for the ingresses should be managed
          tls:
            # provider can be certManager, secret
            provider: certManager
        certManager:
          # the configuration for the clusterIssuer that will be created
          clusterIssuer:
            # the name of the clusterIssuer
            name: letsencrypt-fury
            # the email used during issuing procedures
            email: example@sighup.io
            # solvers definition
            solvers: []

[nutellinoit]

While analyzing the current state of the distro provider together with @smerlos and @Deepzima , we found some additions that are nice to have:

On the distribution side, we have the need to enable or disable stuff, but instead of going to the correct approach

modules:
  networking:
    type: none|calico|cilium
    calico:
      podCidr:
    cilium:
      podCidr:
      nodeNetmask:
  ingress:
    nginx: 
      type: none|single|dual
  monitoring:
    # cannot be disabled
  logging:
    type: none|opensearch-single|opensearch-triple|loki
  auth:
    provider:
      type: none|basicAuth|sso
  dr:
    type: none|on-premises|eks
  policy:
    type: none|gatekeeper

Let's explain:

• modules.networking.type: this field defines if we want to install the networking, by default as none. We need to also add the configurations for calico/cilium (only the cidrs I think are needed here, other stuff can be achieved with customPatches)
• ingress.nginx.type: this field can also be none. if set to none, we won't install the nginx batteries and also we should avoid the creation of the ingresses for the modules
• monitoring cannot be disabled
• logging.type: can be none . If it's none, we just skip the module entirely
• dr.type: this is important for the Distribution provider, because we can define which type of velero installation we want to have, by default, for the distro provider we will use on-premises (as a default on the template) but it can also be none or eks. With eks we expect to put by hand the values that are passed automatically by furyctl in the EKSCluster provider. With none, we will not install it.
• policy.type: can also be none . If it's none, we skip the apply of all the stuff from the policy/opa module (for now, at least)

PS: This applies also to EKS

[nutellinoit]

Opened a related issue: #105

[Al-Pragliola]

Given the new defaults folder, we should delete the file furyctl-defaults.yaml

[omissis]

I left minor comments, LGTM