epic: Quarkus-native developer experience — @CaseType discovery, TaskDefinition sugar, registry shim, live reload

[mdproctor]

Consolidates the remaining Quarkus-native developer experience capabilities from casehub-poc that have not yet been built into this service. Originally tracked as a separate Quarkus extension in casehubio/engine#235; moved here because there is currently one deployable consumer and the extension abstraction is premature until a second consumer appears.

Child issues

• feat: @CaseType CDI qualifier — discover Java-annotated case definition beans #25 — @CaseType CDI qualifier
• feat: TaskDefinition syntactic sugar — higher-level API compiling to Worker + Binding #26 — TaskDefinition syntactic sugar
• feat: CaseDefinitionRegistry shim — YAML and Java-lambda case definition coexistence #27 — registry shim (YAML + Java-lambda coexistence)
• feat: YAML case definition live reload in Quarkus dev mode #28 — YAML live reload in dev mode

Already done (not tracked here)

• Runtime YAML classpath scan and registration — Implement case definition loading — CDI bean discovery and classpath YAML scanning #3 (closed)
• Dev / test profile datasource wiring — in application.properties
• Health check endpoints — Add health check endpoints for k8s liveness and readiness probes #10

Open design questions

• Whether TaskDefinition sugar belongs in api/ (shared) or stays app-local
• Priority/conflict rules when YAML and Java define the same namespace/name/version key
• Whether build-time Jandex scan is worth the complexity over runtime CDI discovery

Links

• Supersedes epic: casehub-quarkus/ — Quarkus extension module (CDI integration, @CaseType, TaskDefinition sugar, Dev Services) engine#235 (closed — moved here, extension approach deferred)
• Partially implemented by Implement case definition loading — CDI bean discovery and classpath YAML scanning #3 (YAML scan + CDI wiring, closed)
• Health checks in Add health check endpoints for k8s liveness and readiness probes #10