feat: Add PostgreSQL 16 as new major and used release version

[ZPascal]

Description:

• The PR adds PostgreSQL 16 to the release, adjusts the CI/CD pipeline, and sets it as the new version in use

TODO:

• Upload the Blobs for PostgreSQL release to the blob store (missing S3 credentials) @beyhan Can you please support me here?
• Test the dev release

Follow-up

• Make the used version used configurable, handled by feat: Add the possibility to specify the used PostgreSQL version #75

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/187427001

The labels on this github issue will be updated when the story is started.

[beyhan]

There is an automation which was introduced for release build with #72 and it will upload the blobs.

[ZPascal]

@beyhan Are you sure that the upload also works in a scratch case? I've got the S3 credentials and can upload the blobs to the blob store.

[ZPascal]

Hi @jpalermo, could you please review the PR?

[beyhan]

Are you sure that the upload also works in a scratch case? I've got the S3 credentials and can upload the blobs to the blob store.

For me it looks like that it will work in general but I'm not sure about this line

postgres-release/ci/tasks/bump-postgres-packages/task.sh

Line 17 in 46d27cf

bosh remove-blob ${OLD_BLOB_PATH}

because OLD_BLOB_PATH will be empty whether the bosh remove-blob command fails it that case. @jpalermo is this intended to do the upload also for the initial major version release?

[jpalermo]

👍

[jpalermo]

v50 was just cut that should have postgres 16 as the default