Update PG_DATABASE_URL to match Service name in k8s manifests

[azaurus1]

Issue Summary

The service name in the Kubernetes manifest for the PostgreSQL database is defined as twentycrm-db. However, the DSN configuration in the Server and Worker deployments incorrectly references twenty-db. This mismatch causes the pods to fail during initialization and crash on boot.

Fix Description

• Updated the DSN values in both the Server and Worker deployments to correctly reference twentycrm-db, ensuring alignment with the database service name.
• Verified the deployments to ensure the pods start without issues after the fix.

Testing

• Deployed the updated manifests in a development environment.
• Confirmed that both Server and Worker pods initialize correctly and connect to the database service as expected.

[greptile-apps]

PR Summary

Updates PG_DATABASE_URL in Kubernetes manifests to correctly reference the database service name 'twentycrm-db' instead of 'twenty-db', fixing pod initialization failures.

• Fixed database service reference in /packages/twenty-docker/k8s/manifests/deployment-worker.yaml and /packages/twenty-docker/k8s/manifests/deployment-server.yaml to match service name defined in service-db.yaml
• Change ensures proper connectivity between server/worker pods and PostgreSQL database service
• Aligns with Kubernetes service naming convention established in the twentycrm namespace

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[FelixMalfait]

Thank you!