feat: Batch entity when persisting [DHIS2-21378]

[enricocolasante]

Summary

Phase 3 of the tracker import Hibernate → JDBC migration (DHIS2-21378). Extends EntityWriteBatch (introduced in
#23970) to also stage top-level entity writes — TrackedEntity, Enrollment, TrackerEvent, SingleEvent, and Relationship — alongside
the TEAV writes already routed through it.

• Scope: inserts and updates for TrackedEntity, Enrollment, TrackerEvent, SingleEvent; inserts only for Relationship (updates are rejected upstream by
  AbstractTrackerPersister, so no stageUpdate overload exists for it). AbstractTrackerPersister now calls stageInsert(...) / stageUpdate(...) instead of entityManager.persist(...)
  / entityManager.merge(...).
• No wire-path behaviour change yet: EntityWriteBatch.flush() still delegates back to EntityManager. Phase 6 swaps this for JDBC multi-row INSERT / unnest UPDATE / tuple DELETE
  statements.
• Flush ordering: top-level entities are flushed before TEAVs so Hibernate assigns ids before any TEAV references them. The top-level order (TE → Enrollment → TrackerEvent → SingleEvent
  → Relationship) matches the persister call order enforced by DefaultTrackerBundleService.commit() and is FK-safe.
• Mark/rollback: Mark now tracks per-type counts via nested EntityCounts / TeavCounts records, preserving the per-entity error-isolation contract used in non-atomic mode.

Notable fix: transient TE in handleTrackedEntityAttributeValues

The cross-persister TEAV dedup lookup (added in Phase 3) issues a JPQL query bound to the owning TrackedEntity. Once TE inserts are also deferred through the batch, a freshly-staged TE has
id == 0 and no DB rows yet — binding it as a query parameter throws TransientObjectException. The lookup now short-circuits to an empty map when te.getId() == 0 and relies on the
batch overlay alone, which is sufficient because a transient TE cannot have any prior TEAVs in the DB or in another persister's session.

Next steps

• Quick fix ✅ formatDate: SimpleDateFormat → static final DateTimeFormatter ─
• Phase 0 ✅ Remove EntityManager from TrackerPersister interface and all method parameters -feat: decouple ChangeLogAccumulator from Hibernate Session [DHIS2-21378] #23836
• Phase 1 ✅ Decouple ChangeLogAccumulator from Hibernate Session; obtain the transaction-bound Connection via DataSourceUtils instead of session.doWork()
• Phase 2 ✅ Extract FileResource assignment update out of AbstractTrackerPersister into FileResourceStore
• Phase 3 ✅ Introduce EntityWriteBatch; accumulate and batch-flush TEAV writes (multi-row INSERT / unnest UPDATE)
• Phase 4 — Pre-allocate IDs from PostgreSQL sequences; stage top-level entity inserts and updates in EntityWriteBatch; remove all entityManager.flush() calls
• Phase 5 — Replace updateTrackedEntitiesLastUpdated named query with NamedParameterJdbcTemplate; remove last Hibernate dependency from DefaultTrackerBundleService
• Phase 6 — Implement JDBC flush methods one entity type at a time (TrackedEntity → Enrollment → TrackerEvent/SingleEvent → Relationship)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud