Release 1.6.0.Beta2

[michalvavrik]

Summary

Release contains:

• Support Jaeger TLS communication with Quarkus OTel OTLP collector configured from TLS registry #1277
• Support TLS registry with Kafka Strimzi for SASL_SSL and SSL scenarios #1276
• Bump io.quarkiverse.artemis:quarkus-artemis-jms from 3.4.1 to 3.4.2 #1274
• Support gRPC TLS communication and TLS registry and FW support for gRPC on same server #1272
• Support OpenShift certificate serving used with TLS registry #1270
• Bump com.puppycrawl.tools:checkstyle from 10.18.0 to 10.18.1 #1269
• Add support for Quarkus CLI TLS command #1268
• Support TLS registry and certificate reloading #1267
• Bump quarkus.platform.version from 3.14.0 to 3.14.1 #1266
• Bump surefire-plugin.version from 3.4.0 to 3.5.0 #1263
• Bump org.apache.maven.plugins:maven-javadoc-plugin from 3.8.0 to 3.10.0 #1264

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Release (follows conventions described in the RELEASE.md)
• 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

[michalvavrik]

run tests

[michalvavrik]

Regarding OpenShift native failures: I just run OCP CI here #1277, it is same HEAD + release commit. There failed different test, therefore it's flaky and not related.

[fedinskiy]

@michalvavrik please create a task in Jira to investigate the failure

[michalvavrik]

@michalvavrik please create a task in Jira to investigate the failure

makes sense @fedinskiy , done https://issues.redhat.com/browse/QQE-951