test(framework): try to fix flaky tests related to postgre db and k8s resource installation

[jijiechen]

Try to fix flaky tests related to postgre db:

• Connect to the newly created database instance before test cases run

Trying to fix this flaky:
https://github.com/kumahq/kuma/actions/runs/7119978753/job/19386239557#step:6:3840

Print more useful information when timeout waiting for k8s Pod to be available:

• print Pod phase and conditions
• print Deployment and ReplicaSet conditions

Trying to help on this flaky:
https://github.com/kumahq/kuma/actions/runs/7116642948/job/19375940607#step:10:25037

Checklist prior to review

• Link to relevant issue as well as docs and UI issues
  • N/A
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS
  • Confirmed
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • N/A
  • Don't forget ci/ labels to run additional/fewer tests
    • Checked
• Do you need to update UPGRADE.md?
  • No need
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label)
  • No backport.