feat: support containers env paramater setting

[cccfs]

CHANGE DESCRIPTION

Problem:
My log-agent generates index configuration by scanning container env and ultimately collects container logs for remote storage, so it needs to support custom pod env configuration

Solution:
Ensure that replica sets and shard mongos support containers env configuration

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?
• Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

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 MongoDB version?
• Does the change support oldest and newest supported Kubernetes version?

[egegunes]

@cccfs implementation LGTM, please add a case for this new field into TestReconcileStatefulSet in pkg/controller/perconaservermongodb/statefulset_test.go

[gkech]

We can simplify this by using golang's unfurl feature

container.Env = append(container.Env, cr.Spec.Sharding.Mongos.ContainerEnv...)

[gkech]

we can do the same for all the related diff changes

[JNKPercona]

Test name	Status
arbiter	passed
balancer	passed
cross-site-sharded	passed
custom-replset-name	passed
custom-tls	passed
custom-users-roles	passed
custom-users-roles-sharded	passed
data-at-rest-encryption	passed
data-sharded	passed
demand-backup	passed
demand-backup-eks-credentials-irsa	passed
demand-backup-fs	passed
demand-backup-incremental	failure
demand-backup-incremental-sharded	passed
demand-backup-physical-parallel	passed
demand-backup-physical-aws	passed
demand-backup-physical-azure	passed
demand-backup-physical-gcp	passed
demand-backup-physical-minio	passed
demand-backup-physical-sharded-parallel	passed
demand-backup-physical-sharded-aws	passed
demand-backup-physical-sharded-azure	passed
demand-backup-physical-sharded-gcp	passed
demand-backup-physical-sharded-minio	passed
demand-backup-sharded	passed
expose-sharded	passed
finalizer	passed
ignore-labels-annotations	passed
init-deploy	passed
ldap	passed
ldap-tls	passed
limits	passed
liveness	passed
mongod-major-upgrade	passed
mongod-major-upgrade-sharded	passed
monitoring-2-0	failure
monitoring-pmm3	passed
multi-cluster-service	passed
multi-storage	passed
non-voting-and-hidden	passed
one-pod	passed
operator-self-healing-chaos	passed
pitr	passed
pitr-physical	passed
pitr-sharded	passed
pitr-physical-backup-source	failure
preinit-updates	passed
pvc-resize	passed
recover-no-primary	failure
replset-overrides	passed
rs-shard-migration	passed
scaling	failure
scheduled-backup	passed
security-context	passed
self-healing-chaos	failure
service-per-pod	passed
serviceless-external-nodes	passed
smart-update	passed
split-horizon	passed
stable-resource-version	passed
storage	passed
tls-issue-cert-manager	passed
upgrade	passed
upgrade-consistency	passed
upgrade-consistency-sharded-tls	failure
upgrade-sharded	passed
users	passed
version-service	failure
We run 68 out of 68

commit: 82b5284
image: perconalab/percona-server-mongodb-operator:PR-1987-82b5284c