[New Feature] GO-Montandon integration

[justinginnetti]

This GitHub ticket is intended to describe the rerouting of the data pipeline for the GO-Montandon/GCDB integration and the redesign of a few components. The deadline for this work is that it needs to be on Production by March 2024 so that we can train the NS how to benefit from it and start using it before this phase of the project comes to a conclusion in September 2024.

At present GO surfaces partners' data via their APIs and S-3 buckets, but in the future we will need to first pull that data into the Montandon, and then surface it on GO from Montandon. (In terms of scope, this ticket does not cover the data pipeline into the Montandon or the preparation of the data there. It is just about data from the Montandon being visualised on the GO front end.)

This integration will facilitate the development of new features and functionality, like (semi-)automated Crisis Categorisation, Field Report and DREF request forms.

Main people implicated from IFRC are @justinginnetti, Hamish and @tovari. @mmusori, @anamariaescobar and @szabozoltan69 are added just for information and for the semi-automated Field Reports and DREF request forms. @frozenhelium and @udaynwa, please feel free to add anyone else from DFS or DevSeed who you think should be here too. @mariam-yu is involved because of the design implications of combining the multiple impact forecasts in one event, for the application of the automated crisis categorisation, and the user journeys for the semi-automated field report and DREF application forms.

Most of the work is described on this Miro board. For the time being, we focus on the components on three pages: Global, Regional and Country pages. The Miro board shows where the data should come from for each of the components related to the Montandon.

[justinginnetti]

1. For the Global page, Risk Watch tab on GO, the data pipeline following components will need to be rerouted:
   

2. For the Regional page, Risk Watch tab, it is the same as for the Global Page.

3. For the country page, however, there are additional components for which the data will need to be rerouted: