[tests] bitnami/postgresql is no longer avaliable

[liran-funaro]

      db_node_failure_handling_test.go:95: starting postgres cluster
      db_node_failure_handling_test.go:95: 
          	Error Trace:	/home/runner/work/fabric-x-committer/fabric-x-committer/service/vc/dbtest/container.go:168
          	            				/home/runner/work/fabric-x-committer/fabric-x-committer/service/vc/dbtest/container.go:83
          	            				/home/runner/work/fabric-x-committer/fabric-x-committer/integration/runner/postgres.go:98
          	            				/home/runner/work/fabric-x-committer/fabric-x-committer/integration/runner/postgres.go:72
          	            				/home/runner/work/fabric-x-committer/fabric-x-committer/integration/test/db_node_failure_handling_test.go:95
          	Error:      	Received unexpected error:
          	            	API error (404): manifest for bitnami/postgresql:latest not found: manifest unknown: manifest unknown
          	Test:       	TestDBResiliencySecondaryPostgresNodeCrash

Following is an announcement on their docker repository bitnami/postgresql.
It seems that we can switch to bitnamilegacy/postgresql for now as an intermediate solution.

⚠️ Important Notice: Upcoming changes to the Bitnami Catalog
This image is part of the brownout announced at https://github.com/bitnami/containers/issues/83267⁠
Beginning August 28th, 2025, Bitnami will evolve its public catalog to offer a curated set of hardened, security-focused images under the new Bitnami Secure Images initiative⁠. As part of this transition:
Bitnami will begin deprecating support for non-hardened, Debian-based software images in its free tier and will gradually remove tags from the public catalog. As a result, community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes
All existing container images have been migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates.
For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images, which include hardened containers, smaller attack surfaces, CVE transparency (via VEX/KEV), SBOMs, and enterprise support.
These changes aim to improve the security posture of all Bitnami users by promoting best practices for software supply chain integrity and up-to-date deployments. For more details, visit the Bitnami Secure Images announcement⁠.