Ingress is hardcoded to AWS ALB and `*.alchemiscale.internal` hostnames

[dotsdl]

In server/alchemiscale-ingress.yaml:

annotations:
  alb.ingress.kubernetes.io/scheme: internal
  alb.ingress.kubernetes.io/target-type: ip
spec:
  ingressClassName: alb
  rules:
  - host: api.alchemiscale.internal
  - host: compute.alchemiscale.internal

This locks the deployment to the AWS Load Balancer Controller and to undocumented internal hostnames. There's no TLS configuration. Other clusters (GKE, AKS, on-prem with nginx-ingress, etc.) need to rewrite this file from scratch.

A templated deployment (#25) would let users override ingressClassName, annotations, hosts, and TLS config. Short of that, at minimum this file needs documentation about which knobs need turning for a non-AWS deployment.