Feature/#68 add tests to frontend

[kylejwatson]

• Adds simple tests to all UI components
• Some tests test styles as there is not much interaction (yet)
• Some of the element finding logic could be extracted out to a page object model
• GroupDataService is untested, we should either go with stubbing fetch calls or msw (I prefer msw).
• Removed unused styling from highlightbox css
• Fixed prop types to limit allowed highlight colors
• Fixed dataPoint interface to use string type
• Made aggregation value type more strict
• Renamed build step for github actions to describe actions taken

[brunocribeiro]

@kylejwatson is it possible to configure something that calculates the coverage, and if the coverage decreases, fail the GH checks? Only coverage doesn't say much, but just to avoid adding code without tests

[kylejwatson]

@kylejwatson is it possible to configure something that calculates the coverage, and if the coverage decreases, fail the GH checks? Only coverage doesn't say much, but just to avoid adding code without tests

Good suggestion, I'll have a look into it for both this and the go code 👍

[brunocribeiro]

@kylejwatson is it possible to configure something that calculates the coverage, and if the coverage decreases, fail the GH checks? Only coverage doesn't say much, but just to avoid adding code without tests

Good suggestion, I'll have a look into it for both this and the go code 👍

Cool. I believe it can be done as part of another task or PR