[bitnami/Ghost] Correctly handle smtpExistingSecret value

[AverageMarcus]

Description of the change

Correctly handles setting either .Values.smtpPassword or .Values.smtpExistingSecret. Default smtp-password is now created in its own Secret if an existing is not provided.

Benefits

Fixes the need to provide a dummy smtpPassword value when using an external secret.

Possible drawbacks

The SMTP secret, if an existing Secret resource is not provided, is now in its own Secret resource rather than the one used for the Ghost auth credentials (to be more in-line with the database secret)

Applicable issues

• fixes [bitnami/ghost] smtpExistingSecret value is ignored #8916

Additional information

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
• Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• All commits signed off and in agreement of Developer Certificate of Origin (DCO)

[alvneiayu]

Thanks a lot for sending a PR. I included some comments.

[alvneiayu]

Hi, the pipelines are failing because you need to keep this. If not you are deploying a deployment trying to get a secret without the key smtp-password because is empty

[alvneiayu]

you need to check here the smtpPassword, you are creating an empty secret without data in this case.

[github-actions]

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.