feat: general configuration, application layout and directory structure

[HendrikThePendric]

This PR is a combination of DHIS2-11283 and DHIS2-11284 plus includes a lot of general project configuration:

• Configure linting, formatting, CI, i18n, jest
• Introduce required dependencies use-query-params and prop-types
• Create a basic layout
• Implement a basic directory structure/ project organisation
• Introduce and auth-wall and cached-resources-provider

A few points to take into consideration when reviewing:

• The directory structure might still change quite a bit over time. What I have tried to do is to organise things "by-function". The app has three distinct sections, a context-selector (top bar), a data-workspace (main content), and an action-bar (bottom bar). These sections will be implemented as components, and all corresponding sub-components will be colocated with these main components. In this particular app I do not expect a lot of components to emerge that are shared across these three sections, but if the do I guess I'll just add a shared folder in the src dir.
• This app only has a single view, so we don't really need a router. We do want to be able to deeplink, so I want the current context-selection-state to be reflected in the query parameters. Hence the inclusion of use-query-params.
• The purpose of the cached-resources provider is not really to reduce network traffic because I am counting on the app-platform to do client side caching soon. It's more to reduce cognitive overhead. Some data is read-only and can be regarded as static from the perspective of the app and it makes sense to just fetch this once the app loads and ensure it is directly available to all components once the app has loaded. This way we don't have to continuously take a loading or error state into account.

[Mohammer5]

IMO the name cached-resources is not really descriptive, it's rather technical. Also, it's not really caching, it's just a wrapper for loading the values and providing them to the rest of the app via context, The data itself is actually "meta data", unfortunately that term already has meaning in the dhis2 context, but it's some form of contextual data. I'm not sure myself what a better description is, but I'd like to raise awareness about this kind of naming in general (e. g. auth-wall is way more descriptive and therefore any dev knows what to expect, at least to some extend)

[dhis2-bot]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀