Try to workaround gdal-data corruption issue

.buildkite/build.sh

@@ -57,3 +57,5 @@ time docker run \
   -w "/src" \
   "${ECR}/ci-tools:latest" \
   sign-debs "/src/build-jammy/*.deb"
+
+mv build-jammy "build-$(dpkg --print-architecture)"

.buildkite/pipeline.yml

@@ -5,13 +5,13 @@ steps:
       - label: "build package (amd64)"
         command: ".buildkite/build.sh"
         artifact_paths:
-          - "build-jammy/*"
+          - "build-*/*"
         agents:
           queue: default
       - label: "build package (arm64)"
         command: ".buildkite/build.sh"
         artifact_paths:
-          - "build-jammy/*"
+          - "build-*/*"
         agents:
           queue: default_arm64
 
@@ -20,18 +20,24 @@ steps:
 
   - label: ":debian: Publish deb"
     command:
+      # attempt to work around gdal-data deb getting corrupted when we download
+      # two of them from the two arch builds at the same time.
+      # This is a likely bug in buildkite agent
+      # TODO: ticket it
+      - mkdir build-collated
+      - mv build-*/*.deb build-collated/
       - >
         aptly-upload
         --aptly-url https://apt-repo.kx.gd
         --retries 3
         --repo kx-builds-jammy
         --series jammy
-        build-jammy/*.deb
+        build-collated/*.deb
     retry:
       automatic: true
     plugins:
       artifacts#v1.2.0:
-        download: "build-jammy/*.deb"
+        download: "build-*/*.deb"
       docker#v1.4.0:
         image: "${ECR}/ci-tools"
         always-pull: true