ci: use same minio image as dev (#1687)

Minio's published image for use in GitHub Actions and other CI platforms is `edge-cicd`.  This has not been updated for 4 years:

* minio/minio#16099

This leads to different errors locally vs CI, which can be confusing: getodk/central#1500

Closes getodk/central#1500

Author: alxndrsn

.github/workflows/s3-e2e.yml

@@ -23,33 +23,17 @@ jobs:
           --health-interval 10s
           --health-timeout 5s
           --health-retries 5
-      minio:
-        # see: https://github.com/minio/minio/discussions/16099
-        image: minio/minio:edge-cicd
-        env:
-          MINIO_ROOT_USER: odk-central-dev
-          MINIO_ROOT_PASSWORD: topSecret123
-          # Enable encryption - this changes how s3 ETags work
-          # See: https://docs.aws.amazon.com/AmazonS3/latest/API/API_Object.html
-          # See: https://github.com/minio/minio/discussions/19012
-          MINIO_KMS_AUTO_ENCRYPTION: on
-          MINIO_KMS_SECRET_KEY: odk-minio-test-key:QfdUCrn3UQ58W5pqCS5SX4SOlec9sT8yb4rZ4zK24w0=
-        ports:
-          - 9000:9000
-        options: >-
-          --health-cmd "curl -s http://localhost:9000/minio/health/live"
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
     steps:
     - uses: actions/checkout@v4
+    - run: make fake-s3-server-persistent
     - name: Set node version
       uses: actions/setup-node@v4
       with:
         node-version: 22.21.0
         cache: 'npm'
     - run: npm ci
     - run: node lib/bin/create-docker-databases.js
+    - run: sudo apt-get install wait-for-it
     - name: E2E Test
       timeout-minutes: 10
       run: ./test/e2e/s3/run-tests.sh

test/e2e/s3/run-tests.sh

@@ -52,6 +52,9 @@ EOF
   read -rp ''
 fi
 
+log "Waiting for fake-s3-server to start..."
+wait-for-it localhost:9000 --strict --timeout=10 -- echo '[test/e2e/s3/run-tests] fake-s3-server is UP!'
+
 NODE_CONFIG_ENV=s3-dev node lib/bin/s3-create-bucket.js
 NODE_CONFIG_ENV=s3-dev make run &
 serverPid=$!