Panache 2 / Hibernate Processor: make sure the JD annotations can be used in place of the ORM equivalents

[FroMage]

Description

Because the ORM equivalent annotations are lacking, for example there's no @Delete annotation, but the JD annotations don't necessarily work for managed and reactive.

Implementation ideas

No response

[quarkus-bot]

/cc @gsmet (hibernate-orm), @loicmathieu (panache)

[yrodiere]

I would be careful about anything that adds "stateful session" meaning to the JD annotations that are meant for stateless sessions.

If Jakarta Data 1.1 adds separate annotations for stateful sessions (@Persist instead of @Insert for example), then I could imagine this becoming a problem...

[FroMage]

Sure, I know that @gavinking insists on those having different names, that's a long debate between us. But until he realises I'm right, there's still @Delete/@Find/@Query that have the same name that need a primary entity to be defined.

[yrodiere]

For cases that use the exact same annotation, sure.

For others... please let's not paint ourselves into a corner.

[FroMage]

Sure.

[FroMage]

Tests added in #52425 which we can only merge once the upstream PR is merged with the fix.

I've tested all interesting annotations and they work regardless of the repo type.

Except, naturally, the new managed entity lifecycle annotations which will only land in JD 1.1.

I suppose I could speed things up by implementing them now, under a temporary Hibernate or Quarkus package name, but given that we have Panache repository equivalents for them, I see no urgency to.