feat: add enrollment dimensions to Event Analytics

[luciano-fiandesio]

DHIS2-20503: Add enrollment dimensions to Event Analytics

Summary

This PR adds support for enrollment-level dimensions in Event Analytics endpoints:

• ENROLLMENT_DATE
• INCIDENT_DATE
• ENROLLMENT_OU

Endpoints:

• /api/analytics/events/query
• /api/analytics/events/aggregate

Changes

1. ENROLLMENT_DATE and INCIDENT_DATE support as both dimension and filter

• Supports fixed/relative periods and operator-based date filters.
• Examples:
  • dimension=ENROLLMENT_DATE:2025
  • dimension=INCIDENT_DATE:THIS_YEAR
  • filter=ENROLLMENT_DATE:GT:2025-01-01
  • filter=INCIDENT_DATE:EQ:NV

2. ENROLLMENT_OU support as both dimension and filter

• Supports:
  • direct UIDs
  • USER_ORGUNIT
  • LEVEL-*
  • OU_GROUP-*
• Uses analytics_rs_orgunitstructure for enrollment OU filtering and name resolution.

3. Join behavior for ENROLLMENT_OU

• When ENROLLMENT_OU is used, query SQL adds:

inner join analytics_rs_orgunitstructure as ous
  on ax."enrollmentou" = ous."organisationunituid"

• Filtering is applied on ous:
  • UID filters via ous."organisationunituid" in (...)
  • Level filters via ous."level" in (...)
• When ENROLLMENT_OU is a requested dimension, select includes:

ous."organisationunituid" as enrollmentou,
ous."name" as enrollmentouname

4. Headers

• Added support for:
  • enrollmentdate
  • incidentdate
  • enrollmentou
  • enrollmentouname

5. Metadata

• Adds metadata items/dimensions for:
  • enrollmentdate
  • incidentdate
  • enrollmentou
• Date field labels use program custom labels when configured.

6. Validation and security

• Event analytics validation accepts ENROLLMENT_OU usage.
• OU constraint handling supports enrollment-OU-based queries correctly.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
2 Accepted issues

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

See analysis details on SonarQube Cloud