Introduce a hibernate reactive variant of the security JPA extension

[mkouba]

Description

The quarkus-security-jpa extension depends on quarkus-hibernate-orm so it would have to live in a separate extension. However, the @Username, @Password and @Roles annotations could be shared.

Implementation ideas

No response

[quarkus-bot]

/cc @DavideD, @Sanne, @gavinking, @sberyozkin

[sberyozkin]

+1, then I can rebuild #22457 around it, as it was of some concern to @stuartwdouglas that security-jpa was not reactive

[geoand]

Definitely +1 for this

[Sanne]

+1

from a usability point of view, it would be nice if it could switch internal implementation automatically, based on the bound datasource being blocking or reactive.

[SetoKaiba]

Any update on it? We still can't use it with reactive?

[egore]

I started working on this a couple of days ago at https://github.com/egore/quarkus-security-jpa-reactive, as a copy&modify approach. Unfortunately I am currently stuck at the QuarkusSecurityJpaProcessor, which still creates the dynamic class using the EntityManager instead of a mutiny session. I think I can steal a good portion from the UserEntityIdentityProvider, but there I had to work around the lack of bySimpleNaturalId of Mutiny.Session.