chore(deploy): reseal dev database-connection secret after doadmin password rotation

[mahdi2ba]

The dev Postgres password for user doadmin changed . The dev SealedSecret database-connection still holds the old password, so this service cannot connect to the database since then.

This PR replaces deployment/overlays/development/database-connection-sealed-secret.yaml with the same connection string re-sealed with the current password. No other change. Prod and test are not touched.

Impact (dev only): keycloak-treetracker-admin-api and treetracker-admin-api return 500 on every DB request (admin-client #1242, admin-api Greenstand/treetracker-admin-api#676).

After merge: ArgoCD syncs the SealedSecret, then the pods must be restarted (delete pods) because the env var is read at start.

Verified: the new password was tested with psql against the dev DB.

[mahdi2ba]

The failed check is not related to this PR. The job dies at actions/checkout@v2 before any test runs: GitHub now forces checkout to Node.js 24, and this workflow runs inside the node:10.18-jessie container, which cannot run it.

This PR only replaces a sealed secret YAML under deployment/, no code. I suggest a separate PR later to update the workflow (newer container image, checkout@v4, setup-node@v4).