More documentation adjustments for new downstream tooling

[gsmet]

@MichalMaler I think this should address your latest concerns.

[MichalMaler]

@gsmet Hello!
Happy to test it as soon as it is merged. :)
Thank you.

[quarkus-bot]

Status for workflow Quarkus CI

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

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

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 integration-tests/virtual-threads/grpc-virtual-threads

✖ io.quarkus.grpc.example.streaming.VertxVirtualThreadTest.testStreamingOutputCall - History

• INTERNAL: Half-closed without a request - io.grpc.StatusRuntimeException

io.grpc.StatusRuntimeException: INTERNAL: Half-closed without a request
	at io.grpc.Status.asRuntimeException(Status.java:533)
	at io.grpc.stub.ClientCalls$BlockingResponseStream.hasNext(ClientCalls.java:631)
	at java.base/java.util.Iterator.forEachRemaining(Iterator.java:132)
	at io.quarkus.grpc.example.streaming.VirtualThreadTestBase.testStreamingOutputCall(VirtualThreadTestBase.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at io.quarkus.test.junit.QuarkusTestExtension.runExtensionMethod(QuarkusTestExtension.java:1018)
	at io.quarkus.test.junit.QuarkusTestExtension.interceptTestMethod(QuarkusTestExtension.java:832)

[gsmet]

@MichalMaler I merged it to main, is it enough for you to test?

[MichalMaler]

@gsmet I will start testing the RHBQ 3.8 docs on the main tomorrow.
Regarding the backport, however, if that will not be a big struggle, I would welcome this to be part of the 3.2, too, but only in a situation where the absence of this mighty fix could bring us trouble. I know you fixed the files directly, and this is an additional assurance.
3.2 is now a safe haven for us, and it would be great to move to main and a larger sample of files when we have fully fixed and debugged the previous release, and with a caution that we can safely use the down-streaming pipeline for 3.2 if needed, even though I would rather not to touch that branch anymore and focus more on the future; but it can of course happen.