chore(self-hosted): remove em-dashes (#48498)

docker/tests/test-s3-backend.sh

@@ -4,7 +4,7 @@
 #
 # Validates that the S3-compatible backend (MinIO, RustFS, etc.) handles
 # all S3 operations that Storage relies on. Uses the aws cli so the test
-# is backend-agnostic — no vendor-specific tools required.
+# is backend-agnostic - no vendor-specific tools required.
 #
 # Usage:
 #   sh test-s3-backend.sh                   # Uses localhost:9100
@@ -82,7 +82,7 @@ s3() {
 }
 
 # Wrapper for jq that yields empty output instead of aborting the suite when
-# the payload is not JSON — an S3 error document, say — and jq exits non-zero.
+# the payload is not JSON (e.g. an S3 error document) and jq exits non-zero.
 jq_r() {
     jq -r "$@" 2>/dev/null || true
 }

docker/tests/test-s3.sh

@@ -3,7 +3,7 @@
 # Test S3 protocol endpoint for self-hosted Supabase Storage.
 #
 # Verifies that the S3-compatible endpoint at /storage/v1/s3 works with
-# standard S3 clients — the same way end users interact with it via
+# standard S3 clients - the same way end users interact with it via
 # aws cli, rclone, or other S3-compatible tools.
 #
 # Usage:
@@ -80,7 +80,7 @@ s3() {
 }
 
 # Wrapper for jq that yields empty output instead of aborting the suite when
-# the payload is not JSON — an S3 error document, say — and jq exits non-zero.
+# the payload is not JSON (e.g. an S3 error document) and jq exits non-zero.
 jq_r() {
     jq -r "$@" 2>/dev/null || true
 }

docker/tests/test-self-hosted.sh

@@ -167,7 +167,7 @@ else
     check "Create user (admin)" "true" "false"
 fi
 
-# Public signup (optional — depends on email autoconfirm setting)
+# Public signup (optional - depends on email autoconfirm setting)
 signup_email="smoke-signup-$$@example.com"
 signup_resp=$(http_body "$BASE_URL/auth/v1/signup" \
     -H "apikey: $ANON_KEY" \

docker/volumes/api/kong.yml

@@ -305,7 +305,7 @@ services:
             - anon
 
   ## Storage API endpoint (with Authorization header transformation).
-  ## No key-auth — S3 protocol requests don't carry an apikey header.
+  ## No key-auth - S3 protocol requests don't carry an apikey header.
   ##
   ## The request-transformer translates opaque API keys to asymmetric JWTs
   ## and passes through existing Authorization headers (user JWTs, AWS SigV4).