Fix Ingress API compatibility (EKS 1.33+) in Intel Helm chart

[danc094codetogether]

Description

Update the Intel Helm chart to deploy cleanly on modern Kubernetes/EKS versions (e.g., EKS 1.33), fixing Ingress API/version detection and enforcing required pathType when using networking.k8s.io/v1.

##Context
While deploying codetogether/codetogether-intel (chart 1.3.0) into EKS v1.33.x, Helm failed with:

no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"

Changes required

Ingress template

• Ensure the chart renders Ingress networking.k8s.io/v1 for K8s versions that support it.
• Always include pathType: Prefix when generating networking.k8s.io/v1 Ingress.
• Keep backward compatibility only if we explicitly want to support clusters <1.19; otherwise simplify logic.

Validation

• helm template must output no networking.k8s.io/v1beta1 for modern clusters.
• helm upgrade --install must succeed on EKS 1.33.x without manual Ingress creation.

Acceptance Criteria

• helm upgrade --install server . -n default -f <values> succeeds on EKS 1.33.x.
• Ingress is created with apiVersion: networking.k8s.io/v1 and includes pathType.
• No references to networking.k8s.io/v1beta1 in rendered output for K8s >= 1.19.

[DavidRS13]

@danc094codetogether @wgalanciak it is testable?

[DavidRS13]

Tested in build v2026.1.1-1786 locally ✅