fix(sec): upgrade org.postgresql:postgresql to 42.5.1

[dack-su]

What happened？

There are 1 security vulnerabilities found in org.postgresql:postgresql 42.3.3

• CVE-2022-31197

What did I do？

Upgrade org.postgresql:postgresql from 42.3.3 to 42.5.1 for vulnerability fix

What did you expect to happen？

Ideally, no insecure libs should be used.

How can we automate the detection of these types of issues?

By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.

The specification of the pull request

PR Specification from OSCS

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[agapple]

tks