refactor: table component

[deansallinen]

Removes the Table component and reverts to using class-based styles on standard html table elements.

Reason: There was no need for the overhead of a component at this stage, with all the prop passing and data typing, when all we're doing is applying styles.

Once I started using the table component for something more complex than displaying tabular data (i.e. the search history) I found there would be too may edge cases and complexity was ballooning.

I think we're better served with the following:

• using standard <table> and associated elements e.g. <td> which are all styled when the .table-styles class is applied to the <table> for all non-interactive tabular data
• if you want to get more complicated e.g. collapsing layouts on mobile, linking rows to pages, etc. then you're better off using a div class="grid" and tailoring the component to the context.

Example: in the search history, the rows needed to be clickable. Using a <a> as a child of <tbody> is not valid. Adding an onclick to the <tr> works, but is not accessible and hard to conditionally style (i.e. showing a pointer cursor only when the row is clickable). So in this case, I used a grid of links styled with the .table-row-styles class to match the appearance of a default table.

This allows for flexibility when needed while keeping simplicity in the base <table> and maintaining consistent styles throughout