Enable PG service binding tests as upstream issue is fixed

[michalvavrik]

Summary

closes: #993

According to quarkusio/quarkus#32773 (comment) the issue was fixed by quarkusio/quarkus#32651.

• sequence change goes down to Hibernate 6
• hippo -> postgresql: it doesn't work with hippo, I think that's because the name is also used for named datasource (so it looks for hippo ds), it is documented at the very end of this page https://quarkus.io/guides/deploying-to-kubernetes#customizing-automatic-service-binding (full disclosure: I'm not sure here. Do you read it same way I do?)

Please select the relevant options.

• Bug fix (non-breaking change which fixes an issue)
• Dependency update
• Refactoring
• Backport
• New scenario (non-breaking change which adds functionality)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[michalvavrik]

run tests

[michalvavrik]

run tests

[michalvavrik]

run tests

[michalvavrik]

run tests

[mjurc]

LGTM with regards to reading the issue histroy. At the same time, this is regression in usability compared to 2.2 even.

SB is tech preview, but still. I'll merge for now, but we should follow up with product issue.

[rsvoboda]

we should follow up with product issue.

+1 ... Is this future 3.2 release related or it affects also next 2.13.z ?

Update: I see #1187, so this is probably no longer relevant question.

[michalvavrik]

no regression, not sure why it didn't work with hippo prev, but it does now #1187