Remove default deployment strategy values

[yardenc2003]

This PR updates the trino/ Helm chart so that coordinator/worker.deployment.strategy is empty by default instead of pre-filled with a RollingUpdate default K8s configurations.

Motivation:

Currently, the chart always renders a .spec.strategy.rollingUpdate block in the deployment manifest, even when users want to use .spec.strategy.type==Recreate. This leads to confusing output, especially when using wrapper charts (in which rollingUpdate is impossible to override) or custom values files (which make you set rollingUpdate to null while using Recreate type).
K8s fails to create the deployment when .spec.strategy.rollingUpdate appears in conjunction with .spec.strategy.type==Recreate.

Solution:

The following changes eliminate the need for workarounds like null to override the rollingUpdate field, making it more flexible and user-friendly.

Backward Compatibility:

The default behavior

strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 25%

is unchanged if users do not override strategy, as these are the default values according to K8s official docs.

[nineinchnick]

I labeled this as a bug because even though there's a workaround, I think it's rather difficult to figure out. Thanks for the excellent PR description!