Migrate from bitnami to bitnamilegacy images

[TessaIO]

Resolves #376

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: ahmed.g.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[TessaIO]

@nineinchnick does the pipeline have a flaky behavior, or is it my change that introduced the failure?

[nineinchnick]

Something's wrong with the new PostgreSQL image. You'll have to try to reproduce this by running tests locally.

[nineinchnick]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[TessaIO]

@nineinchnick I'll fix it in the weekend thanks

[mosabua]

Hey ... I had to do this for Trino Gateway chart .. same approach should work for Trino itself - see #359

In the long run we might have to look for actively maintained alternatives.. we only need minimal stuff really.

[mosabua]

Also we might have to do some of that in trino itself and our docker subproject..

[wendigo]

Restarted build worked fine :) I'm going to merge it!