[artifactory] Create database secrets if postgres password is set

[woodcockjosh]

PR Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• Chart Version bumped
• CHANGELOG.md updated
• Variables and other changes are documented in the README.md
• Title of the PR starts with chart name (e.g. [artifactory])

What this PR does / why we need it:
Allows user to set database password rather than use the generated one. This also works as a workaround for #859

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes

Special notes for your reviewer:

[chukka]

@woodcockjosh I'm not sure this change is required , .Values.database.password implies external postgres

[chukka]

@woodcockjosh This creates a secret for .Values.postgresql.postgresqlPassword from postgresql sub-chart and in statefulset it is referenced using JF_SHARED_DATABASE_PASSWORD

{{ if or .Values.database.secrets.password .Values.database.password .Values.postgresql.enabled }}
        - name: JF_SHARED_DATABASE_PASSWORD
          valueFrom:
            secretKeyRef:
        {{- if .Values.database.secrets.password }}
              name: {{ tpl .Values.database.secrets.password.name . }}
              key: {{ tpl .Values.database.secrets.password.key . }}
        {{- else if .Values.database.password }}
              name: {{ template "artifactory.fullname" . }}-database-creds
              key: db-password
        {{- else if .Values.postgresql.enabled }}
              name: {{ .Release.Name }}-postgresql
              key: postgresql-password
        {{- end }}
      {{- end }}

[woodcockjosh]

right well until a solution is implemented for #859 I'm going to use this approach to fix the problem with upgrades. It would be a shame if everyone else had to copy paste the artifactory chart to solve their problem but I understand if upgrading the chart without the upgrade failing is not the highest priority for the repo.

[woodcockjosh]

@chukka any update on this?

[gitta-jfrog]

We decided to keep the current implementation as it is, if needed, please raise a issue and we will investigate. Thanks!