Remove test workarounds for qhorus reactive activation and Flyway V2 conflict

[mdproctor]

Context

app/src/test/resources/application.properties contains two sets of workarounds for upstream bugs. These should be removed once the upstream issues are fixed.

Workaround 1 — qhorus unconditionally activates Hibernate Reactive

Tracking: casehubio/qhorus#141

casehub-qhorus pulls in quarkus-hibernate-reactive-panache unconditionally. Any non-reactive consumer must suppress it:

casehub.qhorus.reactive.enabled=false
quarkus.datasource.reactive=false
quarkus.datasource.qhorus.reactive=false

Remove when: casehubio/qhorus#141 is resolved and qhorus gates hibernate-reactive behind the build-time flag.

Workaround 2 — Flyway V2 conflict between casehub-work and casehub-qhorus

Tracking: casehubio/qhorus#142 + casehubio/work#162

Both extensions ship a V2 Flyway migration. Flyway refuses to start when both are on the classpath. Workaround disables Flyway and uses drop-and-create in tests:

quarkus.flyway.migrate-at-start=false
quarkus.flyway.qhorus.migrate-at-start=false
quarkus.hibernate-orm.database.generation=drop-and-create
quarkus.hibernate-orm.qhorus.database.generation=drop-and-create

Remove when: Both casehubio/qhorus#142 and casehubio/work#162 are resolved. Restore quarkus.flyway.migrate-at-start=true in test properties and verify schema initialises correctly.

Done when

Both upstream issues resolved, workarounds removed, mvn verify -pl app -am passes.