Bump Quarkus to 2.13.2.Final

[rsvoboda]

Bump Quarkus to 2.13.2.Final

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[rsvoboda]

run tests

[rsvoboda]

Native OCP fails on io.quarkus.qe.OpenShiftStrimziOperatorKafkaWithoutRegistryMessagingIT while JVM one is green.

Kafka related tests seem to be flaky :/

11:13:34,691 INFO oc: 5m33s Normal InstallWaiting clusterserviceversion/strimzi-cluster-operator.v0.31.1 installing: waiting for deployment strimzi-cluster-operator-v0.31.1 to become ready: deployment "strimzi-cluster-operator-v0.31.1" not available: Deployment does not have minimum availability.

[rsvoboda]

SB operator reports Failed status, so there is ENV / Cluster issue

[michalvavrik]

As for non-kafka failures, these runs only succeed with -Dquarkus.native.native-image-xmx=3g in OC runs (with our runners). I didn't change the jobs as it makes a little sense (native runner should have 16 GB memory). Maybe docker memory is not allowed to use all of it. It needs debugging.

[michalvavrik]

I'd suggest Kafka failure is related to pod/kafka-instance-zookeeper-0 Back-off restarting failed container

[pjgg]

run tests

[pjgg]

Must be some cluster degradation because currently is working as expected. Also, is working on my local environment.

[pjgg]

LGTM