bug: S3 Storage: forcePathStyle setting not preventing bucket name from being prepended to endpoint URL

[ianks]

Describe the bug

When using S3-compatible storage (MinIO), the bucket name is incorrectly prepended to the endpoint URL despite having forcePathStyle: true set in the configuration. This causes DNS resolution failures as the system attempts to access {bucketName}.{endpoint} instead of using path-style access ({endpoint}/{bucketName}).

Error encountered:

error Error: getaddrinfo ENOTFOUND logto.s.foo.com
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'logto.s.foo.com',
  '$metadata': { attempts: 1, totalRetryDelay: 0 }
}

Expected behavior

With forcePathStyle: true, requests should be made to s.foo.com/logto instead of attempting to access logto.s.foo.com.

How to reproduce?

1. Configure MinIO or other S3-compatible storage with the following settings:

{
  "bucket": "logto", 
  "endpoint": "https://s.foo.com", 
  "provider": "S3Storage", 
  "accessKeyId": "[redacted]",
  "accessSecretKey": "[redacted]",
  "forcePathStyle": true,
  "publicUrl": "https://s.foo.com"
}

2. Attempt to upload a file or access storage
3. Observe error logs showing attempts to access logto.s.foo.com instead of s.foo.com/logto

Context

• Self-hosted, Logto version = 1.10.0
  • Container (Docker image)
  • Raw Node.js