Cache generation data in frontend

[GoelBiju]

Description:

We need to be able to store generation data in the frontend state especially if we require previous generation data for the visualisation. If we change to storing data in the frontend we can just request the generation data we need by giving a list of the generations to the server and then add the data to the state when we receive it.

This avoids receiving the information we already have and means we won't have to make further requests to the server for the same data during replays or when seeking when using the generation slider.

Acceptance criteria:

• Store generation data in the frontend after requests are made,
• Use the stored data next time it is needed when seeking or replays are made.

[GoelBiju]

The only potential downside to this is storing a lot of information (thousands of arrays of numbers) on the frontend state which could make the client slow but this needs to be tested and this may not be the case. It could be that it does not impact performance too much or there is a faster way of storing large amounts of data in the frontend using other libraries. The other solution would be to have a limit on the maximum data we store on the frontend (or rank it based on which were used last). If we hit the maximum amount of data to store on the frontend, we remove the earliest or the least used data and request the data we need from the server again and store it. This needs to be clarified further.

[GoelBiju]

It is possible to implement to make use of react-query in the future to replace Redux to store the optimisation data. This has inbuilt caching as well.