RabbitMQ `auth.password` is required when `auth.existingPasswordSecret` is defined

[ChristianRaoulis]

Name and Version

bitnami/rabbitmq 14.1.2

What architecture are you using?

None

What steps will reproduce the bug?

1. Create a Secret with rabbitmq-password and a value
2. Set the auth.existingPasswordSecret value to the name of your secret
3. Try to deploy it

What is the expected behavior?

The Chart should use the existing secret values from auth.existingPasswordSecret and don't require the auth.password` value.

What do you see instead?

The Chart shows an error when the auth.password value is empty.

error: template: rabbitmq/templates/secrets.yaml:9:17: executing "rabbitmq/templates/secrets.yaml" at <include "rabbitmq.password" .>: error calling include: template: rabbitmq/templates/_helpers.tpl:69:12: executing "rabbitmq.password" at <include "getValueFromSecret" (dict "Namespace" (include "common.names.namespace" .) "Name" (include "rabbitmq.secretPasswordName" .) "Length" 16 "Key" (include "rabbitmq.secretPasswordKey" .))>: error calling include: template: rabbitmq/templates/_helpers.tpl:293:38: executing "getValueFromSecret" at <"\"">: invalid value; expected string