Parameterize timezone in for hazelcast in values.yaml

[Arul-Devan]

Is your feature request related to a problem? Please describe.
As per INC-B15167, hazelcast service (clustering service) pods are expected to run in the same timezone as pega pods and DB. There is no option to pass the timezone parameter via values.yaml file. Clients are expected to override the entire block of java_opts from the hazelcast cub chart. This is frustrating because this leads maintenance overhead.

Describe the solution you'd like
There should be a way in the helm chart for the clients to pass additional java_opts for hazelcast instead of overriding the whole block.

Describe alternatives you've considered
NA
Additional context
NA