新增 postgresql 連線設定

描述 Description

這支 PR 所做的事情，盡可能詳細取代本文字。 Replace this text and describe This PR doing(Better to be detail)

相關的 Issues #(ticket number) / 無 Related Issues #(ticket number) / None

變更的類型 Change Type

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

影響的 API Affect API

[ ] Challenge
[ ] Submission
[ ] Team
[ ] Round
[ ] 不影響 API No affect API
[ ] 其他（請填寫） Other(Please enter it)

檢查清單 Check List

~~- [ ] 我已經在本地手動測試過，確保功能的完整性和穩定性 I have done fully correct manual test~~

[ ] 我對我的程式碼進行了註解，特別是在難以理解的地方 I have added comment in my code
[ ] 我已經更新了文件，或者我的更改不需要更新文件 I have commented in document
[ ] 我的 PR 有明確的標題與內容描述 My PR has right title and description

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [12327531](https://dashboard.gitguardian.com/workspace/9561/incidents/12327531?occurrence=151650534) | Triggered | RSA Private Key | d73e26281572145549506633cce3204b7565e5d5 | selftest-cert.key | [View secret](https://github.com/sitcon-tw/Camp2024-Drawing-Competition-Backend/commit/d73e26281572145549506633cce3204b7565e5d5#diff-e0f7cf0b73f1093ac1932f0da41b1abf904a19a4b38f9675ec161409b6613849R1) |

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/private_key_rsa#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

sitcon-tw / Camp2024-Drawing-Competition-Backend