Upgrade to Hibernate Reactive 2.0.0.CR1

[Sanne]

Fixes #32533
Fixes #32602

[Sanne]

I'll check what's wrong with security-jpa-reactive ..

[Sanne]

This should be fixed now, some signatures changes in Hibernate Reactive 2.0.0.CR1 and that broke bytecode generated code in the security-jpa-reactive module.

@gsmet N.B. while I'd love this to be backported to the 3.0 branch, the security-jpa-reactive module was introduced in main after the branch. So I've kept the second commit strictly separete, we only need to cherry pick the first one; I hope that's not too inconvenient, sorry for the mess.

[quarkus-bot]

Failing Jobs - Building 91bba01

Status	Name	Step	Failures	Logs	Raw logs
⌛	Native Tests - Security1	Build	⚠️ Check →	Logs	Raw logs

[gsmet]

Thanks for keeping the commits separate and pinging me!

[gsmet]

Unfortunately we cannot backport it because of failures in native. I suspect it has to do with the fact that you upgraded Vert.x while we haven't backported the Vert.x upgrade to 3.0.

/cc @maxandersen @cescoffier the decision to not backport the Vert.x upgrade will probably cause us some headaches here.

[cescoffier]

If it makes things simpler we can backport it. At least it will fix the false-positive snake yaml cve

[gsmet]

I think we will have to do it in the next micro if we want do backport it. It's a bit too late to do it now (I think).

[Sanne]

bummer, yes I assumed since the vertx upgrade was merged we'd be clear to merge the upgrade as well.

It's unfortunate as this HR release solves a great deal of issues and also API was affected.