into workhorse zip_reader_limit_bytes 32-bit truncate issues

Summary

Currently, the Helm chart uses | int when rendering zip_reader_limit_bytes, which silently truncates large values due to 32-bit integer limits. For example, setting 17179869184 (16 GB) results in -2147483648.

Steps to reproduce

into values.yaml try it

gitlab:
  webservice:
    workhorse:
      metadata:
        zipReaderLimitBytes: 17179869184

Configuration used

(Please provide a sanitized version of the configuration used wrapped in a code block (```yaml))

gitlab:
  webservice:
    workhorse:
      metadata:
        zipReaderLimitBytes: 17179869184

Current behavior

into gitlab-workhorse pod config toml will indicate a negative values instead of 17179869184

Expected behavior

need into toml the value specify into values.yaml

Versions

• Chart: 8.11.3
• Platform:
  • Cloud: GKE
• Kubernetes: (kubectl version)
  • Client: v1.31.3
  • Server: 1.32.3-gke.1927009
• Helm: (helm version)
  • Client: version.BuildInfo{Version:"v3.16.3", GitCommit:"cfd07493f46efc9debd9cc1b02a0961186df7fdf", GitTreeState:"clean", GoVersion:"go1.22.7"}
  • Server: