Fix: Set podsecuritycontext values for openshift to supplemental group id

[shreddedbacon]

Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for inclusion in changelog

As #3227 describes, setting fsGroup: 0 in some of our templates does not work in Openshift.

• solr
• elasticsearch
• mariadb-single
• mongodb-single
• rabbitmq
• postgres-single

This sets the podsecuritycontext fsGroup for Openshift to the supplemental group id from the namespace annotations.

Closing issues

closes #3227

[shreddedbacon]

We ran this on a ROSA cluster in a single project using a custom build with the image from this PR. The build ran through fine and provisioned all the deployments using the group ID. Checking other deployments in other namespaces, they all have the supplemental group, and then checking the deployments in this project they look identical in terms of security context settings.