K8SPG-728: Configure s3 to support minio for extensions

[ali3bdalla]

CHANGE DESCRIPTION

Problem:
Extensions storage was not compatible with MinIO due to incorrect S3 configuration.

Cause:
The S3 client did not force path-style addressing, and SSL verification issues were preventing proper connections to the MinIO instance.

Solution:
Updated S3 configuration to support MinIO by enabling path-style addressing and allowing optional TLS verification settings..

CHECKLIST

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?

[it-percona-cla]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[JNKPercona]

Test name	Status
custom-extensions	passed
custom-tls	passed
demand-backup	failure
finalizers	passed
init-deploy	passed
monitoring	passed
one-pod	passed
operator-self-healing	passed
pitr	passed
scaling	passed
scheduled-backup	passed
self-healing	passed
sidecars	passed
start-from-backup	passed
tablespaces	passed
telemetry-transfer	passed
upgrade-consistency	passed
upgrade-minor	passed
users	passed
We run 19 out of 19

commit: 3e6b405
image: perconalab/percona-postgresql-operator:PR-1034-3e6b405ea

[egegunes]

@ali3bdalla thank you for your contribution.

I don't think these changes are enough, because newly added fields won't be used ever.

We need to do the following:

1. Add these new fields into https://github.com/ali3bdalla/percona-postgresql-operator/blob/3e6b405eaece1640fd19a9a6233b48d0ff7e65a5/pkg/apis/pgv2.percona.com/v2/perconapgcluster_types.go#L583-L591
2. Pass these fields' values to extension installer container in https://github.com/ali3bdalla/percona-postgresql-operator/blob/3e6b405eaece1640fd19a9a6233b48d0ff7e65a5/percona/extensions/k8s.go#L63-L93. We need to add these fields only for >= 2.7.0, so please add them conditionally by checking cr.CompareVersion("2.7.0") >= 0
3. Finally pass the flags to extension-installer binary in https://github.com/ali3bdalla/percona-postgresql-operator/blob/3e6b405eaece1640fd19a9a6233b48d0ff7e65a5/build/postgres-operator/install-extensions.sh#L8-L14

[egegunes]

Suggested change

	if(uriStyle == "path") {
	if uriStyle == "path" {