fix: stabilize data engine context

[HendrikThePendric]

Implements N/A

---

Description

This is the problem I hit in the new event-visualizer-app:

1. The dashboard sends a filter change. Our plugin gets new props over postMessage.
2. PluginLoader calls setPropsFromParent. That re-renders the whole tree inside the iframe.
3. DataProvider sits in that tree. Nothing above it is memoised, so it re-renders too.
4. On every render, DataProvider runs new RestAPILink(config) and new DataEngine(link). So useDataEngine() hands out a different engine object than last render.

To avoid this, first we need to ensure config is as stable as possible, which we do by memoizing what we can in dhis2/app-platform#962. And with this stable config we can produce a stable context here.

While the changes in this PR rely on the fix in dhis2/app-platform#962, as well I wouldn't go as far as saying that these two PRs are fully interdependent. This code will run fine without the changes in app-platform. The issue won't be fixed, but it also won't be any worse than things currently are.

[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