Deploy Browsertrix Cloud

[anjackson]

We have been deploying Browsertrix Cloud under K3S. Making this work requires some changes to the base Browsertrix Cloud service so we can deploy locally.

• Must be possible to specify a suitable User Agent string (includings spaces).
  • See Handling of CRAWL_ARGS cannot cope with quoted strings webrecorder/browsertrix-crawler#307 and around
• Must be possible to use a specific set of external DNS name servers.
  • See [Feature]: Allow nameserver override for crawler pods webrecorder/browsertrix#1137
  • Nevermind, setting the DNS config at the K3s level is fine.
• Must be possible to send emails using our internal mail server (Port 25, not TLS, no auth).
  • See [Feature]: Support a wider range of SMTP configurations webrecorder/browsertrix#1136
• If possible, support deployment via Traefik (or re-install K3S using ingress-nginx instead).
  • See [Feature]: Use Path prefix syntax compatible with NGINX or Traefik ingress webrecorder/browsertrix#1135
• Make sure all important configuration has been checked, e.g. WACZ file naming
• Integrate deployment setup+overrides into this repo.

[anjackson]

Still awaiting a 1.7.x official release that includes the SMTP changes we need, but I've restarted the cluster and run a crawl to check the User-Agent and it's all looking good.