fix: conditionally set auto-offset-reset for snuba subscription consumers

[patsevanton]

Description

This pull request addresses an issue where the auto-offset-reset parameter was being unconditionally set for Snuba subscription consumers, even when the value was not explicitly defined in the configuration. This could lead to unintended behavior and potential errors.

To resolve this, I've added a conditional check to ensure that the auto-offset-reset parameter is only included in the command if it is explicitly defined in the values configuration. This change applies to the following Snuba subscription consumer deployments:

• deployment-snuba-subscription-consumer-events.yaml
• deployment-snuba-subscription-consumer-metrics.yaml
• deployment-snuba-subscription-consumer-transactions.yaml

Changes Made

• Added a conditional check around the auto-offset-reset parameter in the command section of each deployment template.
• The parameter is now only included if the corresponding value is defined in the values.yaml file.

Related Issues

• Error: Invalid value for '--auto-offset-reset': '' is not one of 'error', 'earliest', 'latest'. #1537

Related Pull Requests:

• feat(sentry): Add missing --no-strict-offset-reset and --auto-offset-reset for consumers #1535

@Mokto Please review and let me know if there are any additional changes or improvements needed.

Thank you!