feat: show layer alerts in the legend [DHIS2-16362]

[BRaimbault]

Tests ~55% | Style ~5% | Code ~40%

Implements DHIS2-16362
Also prepares/implements:

• DHIS2-7176
• DHIS2-10706
• DHIS2-11926

Stacked on #3783 (Phase 1). Review that one first: this PR only adds the error handling.

Description

Layer errors, warnings and notes are shown in the legend instead of snackbars, in the same place in the app layer card and the dashboard plugin: title, alerts, then the legend.

Alert model

• An alert is { id, severity, title, description?, details? }. Severity is error, warning or info.
• All wording is in one catalog, src/constants/layerAlerts.js. Loaders pick an alert id and never write user-facing text.
• Helpers are in src/util/layerAlerts.js. createLayerAlert(id, { params, details }) builds an alert from the catalog. createLayerAlertFromError(error) turns any thrown error into one, using a single map of DHIS2 error codes shared by all loaders (ERROR_CODE_ALERTS in the catalog).
• Requests add their name to a failed request's error with .catch(throwWithRequest(resource)), so the details say which request failed.
• "Details" shows the HTTP status, error code, server message and request. "Copy" adds the layer, app and server versions and the time, so users can send it to an admin.
• A program, tracked entity type or org unit the user lost access to returns the same "does not exist" error as a deleted one. The wording says "not available" and gives both possible causes. This was checked with a restricted user on 2.43.

Tracked entity layer

• Migrated to the new model, as the first layer type. Other layer types follow, one PR each.
• No more snackbars for this layer.
• Truncation and no-data warnings now show in the app layer card too, not only in dashboards.

Loading, shared by the app and the plugin

• src/hooks/useLoadLayer.js returns loadLayer and canLoadLayer, without redux. loadLayer picks the loader for the layer type and gives it what it needs. It never throws: any layer type that fails finishes loading with an error alert and no data, instead of spinning forever.
• App: useLoadLayerWithRedux (renamed from useLayersLoader) loads the store's layers that aren't loaded yet with useLoadLayer, and stores the results.
• Plugin: Map.jsx loads its layers with useLoadLayer, and LayerLoader.jsx is removed. The fix: dashboard map fixes #3779 fixes are kept: each config loads once, and layers waiting for period types load later. Loads that finish after the views changed are ignored.

Reload

• Alerts are cleared when a layer starts loading again (edit, drill, period sync, data table), so a reloading layer doesn't show the previous result's problems. loadLayer also drops them from the config, so loaders that copy the config can't bring them back.

Developer preview

• Add alertPreview to the URL hash (#/?alertPreview or #/<mapId>?alertPreview) to show every alert on every layer. App only. It lives in src/util/layerAlertsPreview.js, so it can be removed with that file and one call.

---

Quality checklist

Add N/A to items that are not applicable.

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

---

ToDos

• Migrate the other layer types to the alerts model, one PR each. Then remove everything tagged LEGACY-ALERTS (grep -rn LEGACY-ALERTS src), plus useLoaderAlerts.js, LegendAlert.jsx, the old alert codes and loadError.

---

Known issues

• Layer types that are not migrated yet keep their old alerts: snackbars in the app, LegendAlert in the plugin.

---

Screenshots

supporting images

[dhis2-bot]

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

[BRaimbault]

The code comment need review, they should be minimal and cover only essential aspects the tests or the code itself do not clearly convey. Make sure they are timeless (not about development history). Here there is an exception, clearly mark areas that should be removed once all loaders/layers use the new model.

[sonarqubecloud]

Quality Gate failed

Failed conditions
1 New issue
1 New Code Smells (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE