Migrate from NAXA dronetm production instance --> HOTOSM infrastructure

[spwoodcock]

This is costing them money & HOT should be paying for it.

Pt1 S3

• All the data has been transferred from NAXA's dronetm bucket --> HOTs dronetm-prod bucket.
• Only the content of dtm-data was copied across, making that the new root of the bucket.
• The S3 usage / URLs need to be update to:
  1. Remove the dtm-data prefix. ✅
  2. Use the new S3 accelerate URL described in Add S3 transfer acceleration for imagery uploads #699 ✅

Pt2 Database migration

• Create a new database via CloudNativePG in our Kubernetes cluster ✅
• Migrate the existing database --> k8s cluster, as described here https://docs.drone.hotosm.org/dev/migrate-k8s ✅

Pt3 Kubernetes deployment

• Finalise and merge feat(): add helm chart for k8s migration #591 ✅
• Add all env vars and secrets into the cluster via sealed-secrets etc ✅
• Deploy new DroneTM instance to https://drone.hotosm.org via ArgoCD k8s-infra repo ✅

Pt4 Inform users

• Ideally we can have a redirect for now from dronetm.org --> drone.hotosm.org ❌
• Then inform all users of the changed domain (and that all existing data was preserved) ❌

[linear]

TECH-932

[spwoodcock]

https://github.com/hotosm/drone-tm/milestone/5 must be complete before this can go ahead