RHBQ 2.13 -> 3.2 Breaking changes

We will document breaking changes for migration between product versions 2.13 and 3.2 in the RHBQ 3.2 Release Notes the same way we have documented them for previous minor and major releases.

We will curate the list of breaking changes from the wiki and list those changes that affect supported RHBQ features and extensions in the release notes.

QE will review the release notes before publishing downstream with the RHBQ 3.2 release.

To respect the ENG, QE, and Prod teams' workload related to the finalization of the community 3.0 release, we will postpone docs activity on this roughly until the 3.1 community release is out.

We decided to wait until Quarkus 3 has had some community bake time, hoping that most of the severe blocking issues will have been fixed by then and the workload for ENG and QE has decreased to a level that allows for part of the SME's time and attention to be allocated to collaborating with docs on reviews.

We also want to ensure that the content in the upstream wiki has stabilized and can be used as source material for the RN updates without causing excessive workload increases for SMEs.

To protect the QE team's time and capacity, we want the final pre-publishing review to happen in the regular time allocated to docs review in the scheduled Docs Freeze period.

The list of the breaking changes will be extensive, so the review tasks might require slightly more time than they did on previous releases. 

Be advised that the RN are a blocker-level priority docs deliverable for RHBQ 3.2. 

Again, as far as workload and capacity is concerned, Thomas and I will work with QE and ENG SMEs to ensure we have both QE capacity and SME support to deliver this content downstream in time.

We want to stay flexible and non-disruptive, so the logistical aspects of how we do this are negotiable. Likewise, schedules might shift, and unexpected issues might crop up elsewhere. We can address such unexpected changes if and when they occur.

If you have follow-up questions about the information I summarized here, please feel free to reach out with your remarks to Thomas and me.

@Thomas Qvarnstrom, please feel free to add anything I have missed in my summary.