Platform: Helm Charts - Add support for HorizontalPodAutoScaler(HPA) and VerticalPodAutoscaler(VPA) to the airbyte helm charts

[Conall-airbyte]

Describe the feature request

when VPA is configured in a kubernetes cluster, and no VPA resource is defined for the airbyte deployments managed by helm, those deployments would by default be scaled to "0" replicas.

The feature request therefore involves adding support to the airbyte helm charts to create related VPA resources.

Describe the solution you'd like
It would be preferred to have optional native support for VPA or HPA resource definitions to be created when deploying airbyte using our helm charts so that they do not need to manually define scaling policies. instead we should provide some default scaling policies.

Describe alternatives you've considered
The alternative involves the user manually creating resources of type VerticalPodAutoscaler, and applying that during their airbyte deployment pipeline, or creating VPA exclusions to disable autoscaling altogether.

e.g

apiVersion: "autoscaling.k8s.io/v1"
kind: VerticalPodAutoscaler
metadata:
  name: airbyte-webapp-vpa
spec:
  # recommenders field can be unset when using the default recommender.
  # When using an alternative recommender, the alternative recommender's name
  # can be specified as the following in a list.
  # recommenders: 
  #   - name: 'alternative'
  targetRef:
    apiVersion: "apps/v1"
    kind: Deployment
    name: airbyte-enterprise-webapp
  resourcePolicy:
    containerPolicies:
      - containerName: '*'
        minAllowed:
          cpu: 100m
          memory: 50Mi
        maxAllowed:
          cpu: 1
          memory: 500Mi
        controlledResources: ["cpu", "memory"]

Additional context
Offering some level of support for VPA and HPA is a good idea , as these are defacto scaling abstractions in the kubernetes ecosystem, which see widespread usage accross all vendors, incl EKS,AKS,GKS , etc.

Our helm charts previously had this capability, but it was removed as airbyte-enterprise did not exist at that point, and it was deemed out of scope for airbyte OSS:
#15719 (comment)

kubernetes docs on scaling workloads:
https://kubernetes.io/docs/concepts/workloads/autoscaling/