fix: respect user display name preference across metadata queries

[BRaimbault]

Description

Several components ignored the user's Display property setting and always fetched metadata using displayName. This PR threads nameProperty (the transformed API field name: displayName or displayShortName) from useCachedData() through to all relevant queries.

Key changes:

• helpers.js — analysisFields() now accepts nameProperty, fixing dimension item names in saved map configs
• ThematicDialog — was passing the raw setting value (name/shortName) to DataDimension.displayNameProp, which expected the API field name
• OrgUnitsProvider, TrackedEntityPopup, EventLayer, TrackedEntityLayer — queries now use the correct API field name
• LayerLoader — passes nameProperty from context to loaders; eventLoader no longer re-computes the name → displayName transform that CachedDataProvider already performs
• MapView — sources nameProperty directly from context instead of the raw user setting

Not changed (intentionally): programStage, legendSet, organisationUnitLevel, and optionSet remain hardcoded to displayName — displayShortName is not available on these types.

---

Quality checklist

Add N/A to items that are not applicable.

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

[dhis2-bot]

🚀 Deployed on https://pr-3701.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