OpenStack Swift S3 campatible cache

Description

config example (works with Zot Registry, utilizing go sdk)

        "storageDriver": {
            "name": "s3",
            "region": "us-east-1",
            "bucket": "gitlab",
            "secure": false,
            "skipverify": true,
            "accesskey": "gitlab:gitlab",
            "secretkey": "REDACTED",
            "regionEndpoint": "http://127.0.0.1:8090",
            "encrypt": false,
            "v4auth": true,
            "forcepathstyle": true
        }

v4auth and forcepathstyle are mandatory for swift s3 support, but they can not be set

error is:

#4 ERROR: error writing manifest: REDACTED: operation error S3: PutObject, https response error StatusCode: 403, RequestID: txb2669c58fce04c8893d80-0067c5dc0c, HostID: txb2669c58fce04c8893d80-0067c5dc0c, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.
------
 > exporting cache to Amazon S3:
------
ERROR: failed to solve: error writing manifest: REDACTED: operation error S3: PutObject, https response error StatusCode: 403, RequestID: txb2669c58fce04c8893d80-0067c5dc0c, HostID: txb2669c58fce04c8893d80-0067c5dc0c, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

Start by locating the S3 cache/export configuration and its AWS SDK setup; the issue names no file or test. Compare the shown required v4auth and forcepathstyle settings with the current options, then verify that Swift-compatible S3 cache export no longer produces the reported SignatureDoesNotMatch error.