feat: load tracked entities from tracker analytics [DHIS2-16362]

[BRaimbault]

Tests ~70% | Code ~30%

Implements DHIS2-16362

Description

Phase 1 of the tracked entities layer rewrite. This PR targets the feat/DHIS2-16362 integration branch, not master: phases are reviewed separately and released together.

• On 2.41+, the layer loads from analytics/trackedEntities/query, limited to 50,000 rows with a truncation warning.
• 2.40 (no analytics endpoint), layers with relationships and layers filtered by follow-up (analytics supports neither) still use tracker/trackedEntities. canLoadTrackedEntitiesFromAnalytics makes that choice.
• Geometry comes back as WKT, parsed with betterknown, so polygon tracked entity types keep working. geometryOnly=true is used, because coordinatesOnly=true drops polygons.
• Both APIs share one set of filters (getTrackedEntityFilters), so program status, follow-up and period follow the same rules.
• Server version differences go through util/versionToggle.js and are tagged VERSION-TOGGLE.
• Errors show on the layer card (loadError) instead of leaving the layer loading.
• teiRelationshipsParser.js is renamed to trackedEntityRelationships.js and now also loads relationships.

Behavior changes:

• 2.41+ layers without a saved org unit mode now include all org units below the selected ones, matching Line Listing. 2.40 keeps "Selected only".
• Follow-up now filters on 2.41+ (it was silently ignored), and an unchecked box no longer hides tracked entities marked for follow-up.
• On 2.41+, data is as fresh as the last analytics table run.

src/util/versionToggle.js is also added by #3707. Whichever merges second keeps both sets of functions.

---

Quality checklist

Add N/A to items that are not applicable.

• Dashboard tested
• Cypress and/or Jest tests added/updated
• Docs added N/A
• d2-ci dependencies replaced N/A
• Tester approved (name)

---

ToDos

• Test point (Malaria Entity) and polygon (Focus area) tracked entity types
• Test on 2.40 and 2.41+
• Test a layer with relationships, and one with follow-up checked
• Test the error on a server without tracked entity analytics tables

---

Known issues

• Tracker analytics has no follow-up filter, so follow-up layers use the tracker API (dhis2-core ticket to file)
• Tracker analytics returns WKT geometry instead of GeoJSON like events and enrollments (dhis2-core ticket to file)
• Relationship types that don't link two tracked entities show a load error (fixed in the Phase 2 relationships rewrite)

[dhis2-bot]

🚀 Deployed on https://pr-3783.maps.netlify.dhis2.org

[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