Heatmap component additions

[ddelpiano]

• The component is currently deployed but not working, returns a 502 when requesting an heatmap.

• The scroller should impact only the left sidebar with all sections.

• The heatmap generated should be on top rather than vertically centred.

• The cord image should be resized (as per mockups)

• Borders should be slightly rounded

• connect the component to the sidebar toggle

[zsinnema]

@ddelpiano the 502 is because the generation of the heatmap is consuming too much cpu and memory. The cordmap team should optimize it to use at least 10x less resources. As an example on our dev cluster it takes 20 seconds to generate the map. This means that during these 20 seconds no other request can be processed on the worker. Of course we could try to implement other kind of workers (e.g. async workers) but that would not help us since the cpu and memory is occupied.

If the cordmap team can't come up with a solutions we have to think about other ways to decouple the computation from the web backend servert (e.g. use argo workflows)

cc: @afonsobspinto