Adding some additional conditionals for the TLS guide

[MichalMaler]

Based on QE feedback, I am applying some additional conditionals to reuse this content further.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 2ff9f1e.

✅ 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.

[github-actions]

🙈 The PR is closed and the preview is expired.

[MichalMaler]

This will need to be backported to 3.15.

[jmartisk]

I'm not particularly happy about this being in the upstream docs, but... yeah. If it's a product requirement that we can't achieve in other ways...

(If we go on adding these things, I'm scared it may explode horribly)

[MichalMaler]

@jmartisk @cescoffier
Hello!

1. This is just a cosmetic PR and the follow-up of:

• Adding content conditionals for the TLS guide #43658
• [3.15] Adding content conditionals for the TLS guide #43675

2. Look, I don't like it either, but when Quarkus and downstreamed product differ in what is supported and allowed, there is simply no other option.

Moreover, any activities related to tooling and scripting have been prohibited (for us, writers), so these workarounds using attributes, #ifdef, and #ifndef conditionals are the only way to maintain the rendered Quarkus as it is while obtaining different behavior in RHBQ.

Please merge if there are no other objections. I am also for finding of a better solution in the future, but Quarkus dev help will be required. This is the best the docs team can do on their own.

[rolfedh]

Small nit. LGTM

[MichalMaler]

This is not needed since the , you are suggesting here is present in the next line: