Description
See https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html
AWS noted that postgres 16.4 is moving toward end of support and will be unable to re-deploy, updating to 16.9

You are receiving this message because you have one or more instances running Amazon RDS for PostgreSQL minor versions 13.15, 13.16, 14.12, 14.13, 15.7, 15.8, 16.3, or 16.4 that require your attention. The mentioned Amazon RDS for PostgreSQL minor versions will reach end of standard support on October 31, 2025. To learn more about the RDS policies related to major and minor version support, refer to Database Engine Versions section in RDS FAQs [1].

Starting October 1, 2025, you will not be able to create new instances with RDS for PostgreSQL minor versions 13.15, 13.16, 14.12, 14.13, 15.7, 15.8, 16.3, or 16.4 from either the AWS Console or the CLI. RDS will upgrade your databases running versions listed above to PostgreSQL 13.18, 14.15, 15.10, 16.6, or higher during a scheduled maintenance window after October 31, 2025.

We recommend that you take action and upgrade [2] your Amazon RDS for PostgreSQL databases running minor versions 13.15, 13.16, 14.12, 14.13, 15.7, 15.8, 16.3, or 16.4 to versions 13.18, 14.15, 15.10, 16.6, or higher before October 31, 2025 [3]. Alternatively, you can enable Automatic Minor Version Upgrade [4] to allow Amazon RDS to upgrade your instances.

This is a mandatory engine version upgrade and it requires downtime. To minimize the downtime during the upgrade, you can now use the fully managed Amazon RDS Blue/Green Deployments that uses physical replication for minor version upgrades [5].

Review Instructions
Dockstore should build and function as normal

Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-7225

Security and Privacy

None, should be improvement

• Security and Privacy assessed

e.g. Does this change...

• Any user data we collect, or data location?
• Access control, authentication or authorization?
• Encryption features?

Please make sure that you've checked the following before submitting your pull request. Thanks!

• Check that you pass the basic style checks and unit tests by running mvn clean install
• Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
• Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
• If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
• Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
• Do not serve user-uploaded binary images through the Dockstore API
• Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
• Do not create cookies, although this may change in the future
• If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.