Switch to Gradle component variant-based approach to resolve conditional and deployment dependencies

[aloubyansky]

Fixes #48992

Quoting the doc update added as part of this PR:

disableQuarkusComponentVariants project property was introduced in Quarkus 3.26.0 to control whether Quarkus component variants should be added to certain dependencies of a project to enable link:conditional-extension-dependencies.adoc[Quarkus conditional] and build time (deployment) dependencies. Quarkus component variants are enabled by default since 3.26.0.

The approach to enable Quarkus conditional and extension build time (deployment) dependencies has changed in Quarkus 3.26.0 due to a few issues with the previous implementation.
Specifically, the previous implementation would not apply relevant dependency exclusions to enabled conditional and deployment dependencies. It would also appear to leak devmode-only dependencies into non-devmode classpaths (such as test and prod) in some cases. These issues couldn't be fixed in a reasonable way in the previous implementation, which is why the Quarkus dependency resolution had to be re-implemented based on a different approach using link:https://docs.gradle.org/current/userguide/variant_attributes.html[Gradle component variants].

The previous implementation still remains available for now in case the new one appears to introduce not yet detected regressions and can be enabled by setting disableQuarkusComponentVariants project property to true.

[aloubyansky]

@reaver585 fyi. It'd be great if you could also review this one. Thanks!

[github-actions]

🙈 The PR is closed and the preview is expired.

[aloubyansky]

'''
link:conditional-extension-dependencies.adoc[Quarkus conditional]
'''
doesn't appear to work in the preview

[gsmet]

You have to use xref:.

[gsmet]

I will fix it as it's going to be annoying for multi-version doc.

[aloubyansky]

Updated the links in the docs

[aloubyansky]

Updated versions in the docs to 3.25.1, since this is the target now.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 01d1bcf.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 01d1bcf.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[LarsSven]

@aloubyansky since you state:

The previous implementation still remains available for now in case the new one appears to introduce not yet detected regressions

Was this PR supposed to be frictionless to users? Because our extension started failing after this change.

https://gitlab.com/rug-digitallab/resources/quarkus-signalr/-/merge_requests/160

[aloubyansky]

@LarsSven sorry to hear that and glad the switch to the previous impl still works for you (afaiu).
Please create a new issue with the details of the regression in your project and how it could be reproduced. A reproducer would be highly appreciated. Thanks!