Use Quarkus Platform BOM

[vmuzikar]

Closes #20570
Closes #15870
Closes #9075

Supersedes #21078
Changes from the original PR:

• Rebased to resolve conflicts
• Quarkus 3.2.0.Final is used instead of 3.2.0.CR1
• I sneaked in more of the dependencies clean-up (to resolve Remove any unnecessary dependency from distribution #9075). This could be split into a separate PR if desired.

Umbrella for post-22 follow-up issues: #21356

This is currently blocked as we're waiting for the release of Quarkus Platform BOM for 3.2.0.Final

[vmuzikar]

In order to merge this, we need reviews from @keycloak/store and @keycloak/core.

@miquelsi Could you please confirm the QE pipelines are happy with this change?

@ASzc Could you please confirm it's ok for prod?

@abstractj Can you please double check the dependencies upgrades/downgrades are ok from CVEs perspective?

@pedroigor With regards to #9075, I currently went the simple path and excluded the Quarkus dev services on mvn level (without using profiles). Are you aware of any use cases we need the dev services for during development currently?

[sguilhen]

Thsanks @vmuzikar ! I'm ok with the much needed cleanup being in this PR - don't think we need a separate one just for that.

From store perspective, it should be ok!

[ASzc]

I see com.fasterxml.jackson.core:jackson-core and com.fasterxml.jackson.core:jackson-annotations are being removed? There are some product build parameters related to those two, specifically forcing version 2.13.4.redhat-00002, I can't remember why. If they're being removed then easy enough to drop these related build parameters too.

I also see there are some new exclusions for deployment dependencies. That's good, in theory should help clean up non-RHBQ jars in our zip.

Otherwise seems ok. Ideally with the volume of pom changes a trial product build would be performed before merging this PR, but we don't have automation for that yet. If you're interested in doing it manually I can guide you, otherwise I'll fix any errors that crop up in the nightly build after this is merged

[ahus1]

Reviewed the changes, thank you for this cleanup. I see that the distribution is now down to 168 MB instead of 188 MB, which is great.

I did a short local test, and it looks fine to me. Thanks!

[ahus1]

Reviewed the changes, thank you for this cleanup. I see that the distribution is now down to 168M instead of 188 MB, which is great.

I did a short local test, and it looks fine to me. Thanks!

[vmuzikar]

Thanks for all the reviews!

@miquelsi Just wanted to double check if you were able to run the internal pipelines with this.