K8SPG-624 Add support for S3ForcePathStyle and verifyTLS for custom extensions

[gkech]

CHANGE DESCRIPTION

Problem:

When installing external extensions, the storage configuration is missing the options for force path style and SSL enabling. We should introduce these options so that S3 compatible storages can be used for storing external extensions.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:

Sample CR:

  extensions:
    image: perconalab/percona-postgresql-operator:main
    imagePullPolicy: Always
    storage:
      type: s3
      bucket: pg-extensions
      region: eu-central-1
      endpoint: s3.eu-central-1.amazonaws.com
      forcePathStyle: false
      disableSSL: false

Notice this

      forcePathStyle: false
      disableSSL: false

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?
• Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
• Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

• Is an E2E test/test case added for the new feature/change?
• Are unit tests added where appropriate?

Config/Logging/Testability

• Are all needed new/changed options added to default YAML files?
• Are all needed new/changed options added to the Helm Chart?
• Did we add proper logging messages for operator actions?
• Did we ensure compatibility with the previous version or cluster upgrade process?
• Does the change support oldest and newest supported PG version?
• Does the change support oldest and newest supported Kubernetes version?

[nmarukovich]

Maybe it's better to use separate bucket to store extensions.

[hors]

@nmarukovich it is a temporary minio deployment

[pooknull]

LGTM. I'll approve after the shfmt warning fix

[gkech]

LGTM. I'll approve after the shfmt warning fix

fixed, 1757812