Support Hibernate DevUI HQL Console for Hibernate Reactive

[mbellade]

Description

Following up on #39584, we now have a DevUI interface that allows querying data and testing arbitrary HQL statements with Hibernate ORM.

Currently, Hibernate Reactive is not supported by this interface (see #48477), but it would be nice to also enable the console for developers that only use the Reactive version of Hibernate's APIs. Implementation should be relatively easy, we just need to find a way to override the executeHQL method in HibernateOrmDevJsonRpcService to use Reactive instead of ORM.

Implementation ideas

No response

[quarkus-bot]

/cc @DavideD (hibernate-reactive), @cescoffier (devui), @gavinking (hibernate-reactive), @phillip-kruger (devui)

[yrodiere]

I think ideally, for PUs that are both blocking and reactive, we'd allow switching.

I'm not sure how we'd expose that, though:

1. We could keep everything in a single page, add "ORM/Reactive" labels next to PUs for information, and add a toggle button in the console to switch between the two modes
2. Or... we could just duplicate the dev UI and have one for Hibernate ORM and another for Hibernate Reactive.

Option 1 could be confusing, but option 2 could be inconvenient, so... to be pondered.

[phillip-kruger]

You can create reusable web components in a shared module (if one exists) and let each have their own ui that use these components

[yrodiere]

Oh right I'm sure that's doable without duplicating too much code, I meant "duplicating what the user sees".

And when I said inconvenient, I meant for the user: I wonder how badly people will want to swtich from ORM (blocking) to Reactive.

Maybe we should do both: have two pages, but an easy way to switch from one to the other.

[mbellade]

I believe adding some form of (reactive) or (orm) labels to the existing persistence unit combo-box would be clean and intuitive for the users, since the reactive/blocking usage of Hibernate is tied to a PU. I wouldn't go as far as having two different pages, unless there's something worth changing the UI's design for between the two versions, but I can't think of anything like that.