[BUG] S3 storageprovider doesn't support path style access

[leonliao]

Describe the bug
Tried to use s3/oss storageprovider to create backuprepo to store backup into own-made S3 compatible object storage service, which only supports the path-style access. But the backuprepo failed to pass the pre-check, because of the pre-check always uses virtual hosted style to access S3 service.

To Reproduce
Steps to reproduce the behavior:
1.

kubectl create secret generic s3-credential-for-backuprepo \
  -n default \
  --from-literal=accessKeyId=xxxPLE \
  --from-literal=secretAccessKey=wJyyyyyyyyyyPLEKEY

create backup repo

apiVersion: dataprotection.kubeblocks.io/v1alpha1
kind: BackupRepo
metadata:
  name: my-repo
  annotations:
    dataprotection.kubeblocks.io/is-default-repo: "true"
spec:
  storageProviderRef: s3
  accessMethod: Tool
  pvReclaimPolicy: Retain
  volumeCapacity: 100Gi
  config:
    bucket: backupbucket
    endpoint: "http://s3-compatible.internal.objectstorage.com"
    region: Useless
  credential:
    name: s3-credential-for-backuprepo
    namespace: default

3. failure

Error: push to "/precheck.txt": RequestError: send request failed
caused by: Put "http://backupbucket.s3-compatible.internal.objectstorage.com/": dial tcp: lookup backupbucket.s3-compatible.internal.objectstorage.com  on 10.96.0.10:53: no such host

Desktop (please complete the following information):

• OS: Linux
• Version 0.9.2

[zjx20]

The s3 StorageProvider is for the AWS S3 service. For self-hosted S3-compatible services, use the minio StorageProvider instead.

[leonliao]

The s3 StorageProvider is for the AWS S3 service. For self-hosted S3-compatible services, use the minio StorageProvider instead.

OK. Will try. I thought adding force_path_style to enable the path-style