Backport of chore(tests): bump the postgres version used in CI into release/0.21.x

[hc-github-team-secure-boundary]

Backport

This PR is auto-generated from #6763 to be assessed for backporting due to the inclusion of the label backport/0.21.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@emilia-grant
This person should resolve the merge-conflict(s) by either:

• Manually completing the cherry picks into this branch
• Creating a new branch and manually cherry-picking all commits being backported

merge conflict error: POST https://api.github.com/repos/hashicorp/boundary/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Description

This PR

• Bumps the default version of postgres used when calling make test-database-up from postgres 12 to 16.
  • I chose 16 because our support for 15 ends in 3 months.
• Adds dockerfiles for postgrest 17 and 18
• Fixes tests that broke due to dependence on the order of results returned by the db. Some changes were made in pg 14 that exacerbated this. As far as I can tell, the business logic being tested doesn't seem to care but I'm a bit out of my depth on that.

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.
• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've documented the impact of any changes to security controls.
  Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

---

Overview of commits

• 5cd7bcb

• fc87160

• e43f86c

• c4fc07e

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

1 out of 2 committers have signed the CLA.

• emilia-grant
• temp

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}