Gitlab object storage regionendpoint should be independent of endpoint

Bug

Description

Describe the problem, what were you doing when you noticed the bug?

This PR 3c81b58e was great in that it allowed gitlab endpoints to be set independently of other conditions, however, the logic for regionendpoint on line 42/43 should be completely independent of this as it causes issues with the gitlab registry if a custom endpoint is set. The registry regionendpoint value is not the same as the other endpoint value and will cause the registry pod to crash until we patch the gitlab object storage secret with regionendpoint removed. Recommend opening another value for regionendpoint since it functions differently

Provide any steps possible used to reproduce the error (ideally in an isolated fashion).

Set a custom s3 endpoint in the values for gitlab object storage and observe that both endpoint and regionendpoint are set in the gitlab object storage secret In our environment, this caused registry pod to not be able to come up until the object storage was manually patched without regionendpoint.

BigBang Version

What version of BigBang were you running? Has been occurring since that MR, which was approx 2.43 but still exists in latest.