[PM-9332] Added optional topologySpreadConstraints configuration

[lidiams96]

Description

This pull request introduces optional configuration for topologySpreadConstraints in the Helm chart for better control over pod distribution across nodes.

Changes Made

• values.yaml: Added topologySpreadConstraints: [] to each component block, allowing users to define topology spread constraints if needed.
• templates/component.yaml: Included logic to render topologySpreadConstraints from values.yaml if specified.

Benefits

These changes provide the flexibility to specify pod distribution constraints, improving resilience and availability by ensuring pods are evenly spread across failure domains.

Backwards Compatibility

The default configuration keeps topologySpreadConstraints empty, ensuring no impact on existing deployments that do not require this feature.

[bitwarden-bot]

Thank you for your contribution! We've added this to our internal Community PR board for review.
ID: PM-9332

[bitwarden-bot]

Checkmarx One – Scan Summary & Details – 47b51263-7425-44e8-bc45-7f99b9e1c8ff

No New Or Fixed Issues Found

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}