Resolves split package on health package issue #38711

(cherry picked from commit e530ff1)

(cherry picked from commit 0a7e34f)

(cherry picked from commit abf03b2)

Co-authored-by: George Gastaldi <gegastaldi@gmail.com>
(cherry picked from commit 78906ad)

Fixes: #39041
(cherry picked from commit 86fc0b2)

(cherry picked from commit e35739f)

(cherry picked from commit f3f18eb)

(cherry picked from commit b5dff7a)

(cherry picked from commit 6a29b34)

(cherry picked from commit d2b25c8)

The simple `xref:file.adoc` macros were not being processed.

(cherry picked from commit 9f48ab5)

(cherry picked from commit a3bc395)

(cherry picked from commit 1002624)

(cherry picked from commit 11bd532)

(cherry picked from commit 105fc00)

(cherry picked from commit 366a981)

(cherry picked from commit e3f2004)

(cherry picked from commit 46cf7f5)

(cherry picked from commit a807eb5)

(cherry picked from commit 07bfe63)

(cherry picked from commit 22a463b)

(cherry picked from commit f83ad85)

Fixes: #19849
(cherry picked from commit bd77018)

…t resolver

(cherry picked from commit 95ff1c8)

Note that I was a bit surprised that we are copying some transformed
jars in the lib/main directory.
Apparently, only jars for which we remove entries.
From my tests, the entry removal is reproducible and always produces the
exact same binary so I suppose it's good enough.

Fixes #39130

(cherry picked from commit e5eb989)

…se mock injection

(cherry picked from commit 986244b)

This update brings significant changes affecting extensions utilizing a (Vert.x) TCP client. With Vert.x version 4.5.4, establishing TLS connections now mandates the use of hostname verification algorithms. This requirement impacts various components including Reactive SQL clients, Redis, RabbitMQ, MQTT, among others.

Previously, if not explicitly specified by the protocol, the verification algorithm defaulted to "". This setting essentially skipped the verification process. However, with the new version, explicit configuration is necessary. Consequently, each extension has been adjusted to utilize the most appropriate verification algorithm.

It's important to note that these modifications may potentially disrupt existing applications. In such cases, referring to the documentation of the specific extension or component is recommended for proper configuration of the hostname verification algorithm.

(cherry picked from commit ee8b09a)

(cherry picked from commit 11824c7)

… not break)

The update to Vert.x 4.5.4 necessitates adjustments in extensions leveraging the Vert.x TCP client, notably impacting reactive SQL clients. TLS connections now require explicit configuration of hostname verification algorithms.

Previously, in the absence of explicit specification by the protocol, the verification algorithm defaulted to "". Although this default remains unchanged in this commit, a MicroProfile Config limitation (microprofile/microprofile-config#446) highlights that "" is not a valid value in the Quarkus configuration. Consequently, "NONE" has been adopted as an alternative. This enables users to explicitly set the hostname verification algorithm to "NONE" to bypass the verification process.

(cherry picked from commit db68332)

This update addresses the breaking changes introduced by Vert.x 4.5.4 for MQTT and RabbitMQ integration regarding hostname verification.

To maintain backward compatibility, hostname verification is still disabled by default. However, to provide users with flexibility and security options, this version introduces connector options to activate hostname verification without using the programmatic customization.

(cherry picked from commit 6e4dee7)

This version aligns the Vert.x and Netty versions.

(cherry picked from commit 261d756)

- fixes #39169

(cherry picked from commit 3aecefb)

…ring for dev mode launch

(cherry picked from commit 5563998)

Resolves
#39120

(cherry picked from commit 809c48c)

3.8.2 backports 1

(cherry picked from commit ca63e5c)

(cherry picked from commit 2d04805)

(cherry picked from commit 048556b)

Bumps `quarkus-http.version` from 5.2.0.Final to 5.2.1.Final.

Updates `io.quarkus.http:quarkus-http-vertx-backend` from 5.2.0.Final to 5.2.1.Final

Updates `io.quarkus.http:quarkus-http-core` from 5.2.0.Final to 5.2.1.Final

Updates `io.quarkus.http:quarkus-http-http-core` from 5.2.0.Final to 5.2.1.Final

Updates `io.quarkus.http:quarkus-http-servlet` from 5.2.0.Final to 5.2.1.Final

Updates `io.quarkus.http:quarkus-http-websocket-vertx` from 5.2.0.Final to 5.2.1.Final

Updates `io.quarkus.http:quarkus-http-websocket-core` from 5.2.0.Final to 5.2.1.Final

---
updated-dependencies:
- dependency-name: io.quarkus.http:quarkus-http-vertx-backend
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.quarkus.http:quarkus-http-core
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.quarkus.http:quarkus-http-http-core
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.quarkus.http:quarkus-http-servlet
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.quarkus.http:quarkus-http-websocket-vertx
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.quarkus.http:quarkus-http-websocket-core
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
(cherry picked from commit 545e5ea)

3.8.2 backports 2