fix: postgres secret key

[bastiaanv]

Please provide enough information so that others can review your pull request:

fixing a typo in the postgres sercet key for Stateful postgres version:

Explain the details for making this change. What existing problem does the pull request solve?

The generated secret in my k8s is;

apiVersion: v1
kind: Secret
metadata:
  name: wbe-frappe
type: Opaque
stringData:
  postgres-password: ***

Note that this secret creates postgres-password instead of postgresql-password

[greptile-apps]

Confidence Score: 4/5

The key correction is consistent, but the repository’s regression-test requirement should be satisfied before merging.

_{Reviews (1) · Last reviewed commit: "fix: postgres secret key"}

[greptile-apps]

Missing PostgreSQL regression coverage

Both PostgreSQL site-creation jobs should be rendered in tests and checked for secretKeyRef.key: postgres-password. Current CI exercises only the single-site MariaDB branch, so this typo could recur undetected. This violates the repository requirement that bug fixes include regression coverage and must be addressed before merging.

Context Used: Guidelines for reviewing Frappe Framework applications. (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: erpnext/templates/job-create-site.yaml
Line: 157

Comment:
**Missing PostgreSQL regression coverage**

Both PostgreSQL site-creation jobs should be rendered in tests and checked for `secretKeyRef.key: postgres-password`. Current CI exercises only the single-site MariaDB branch, so this typo could recur undetected. This violates the repository requirement that bug fixes include regression coverage and must be addressed before merging.

**Context Used:** Guidelines for reviewing Frappe Framework applications. ([source](https://github.com/frappe/skills/blob/main/skills/quality-code-review/SKILL.md))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.