Feature/f 158 linechart component additional functionalities for forecast

[plaume8]

F-158 Linear

I have now added some functionalities to the LineChart that make it clean and easy to distinguish between forecast and non-forecast data.
On the /elements page, I’ve added three proposals for how a chart, including a forecast line, could look like.

However, I don’t think it makes sense to explicitly add extra parameters to the LineChart component to handle forecast data.
The components using the LineChart should be responsible for correctly setting the LineChart parameters. For example, the FSC component would be responsible for fetching the data and correctly setting the LineChart component's parameters (eg determining which line is dashed and which is not).

[netlify]

✅ Deploy Preview for wfp-hungermap ready!

Name	Link
🔨 Latest commit	95dca63
🔍 Latest deploy log	https://app.netlify.com/sites/wfp-hungermap/deploys/675753c22a27590008504e46
😎 Deploy Preview	https://deploy-preview-116--wfp-hungermap.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[bohdangarchu]

I still think we need a consistent way of showing forecast data that is handled by the linechart component. Otherwise we might have a situation where every component is repeating the same code, or every component has different way to show prediction. My suggestion would be to add a flag or type to lines parameter indicating that a line is a forecast or not. And LineChart would apply the styles based on that. By the way I like the styling you applied, especially this one

[plaume8]

@bohdangarchu @marinovl7 - I added the additional params predictionVerticalLineX and lines.prediction such that the prediction styling is automatically applied

note: the LineChartOperations is becoming quite big and complex -> i will refactor it a bit in F-165

[bohdangarchu]

good job!

[marinovl7]

LGTM!