Add issues table component to issues details page

Context:

The current implementation of the dataset issues page is that we're playing issues back to users on a per-entity / per-record basis, meaning that users have to click through each entity/record to view the details of the issue.
This isn't a great user experience when the user is faced with a high volume of issues.
A better experience would be to display this data back to them in an aggregated format, in a table.
The intention is to re-use the component from the check tool, so that we don't have multiple versions of the same thing floating around, and only have to maintain styles in one place: https://github.com/digital-land/submit/issues/421

The table view will be the default view for the issues details page.
Users will navigate to the issues entity page from the issues table. The table should include a link to the entity-level view, to each specific entity.
The table view the same as the current entity-level view, except that the entity table is replaced with the aggregated table.
Each view should have their own pagination as well (table view might not always need it shown if all rows fit on a single page).
In terms of column ordering in the table: reference should show first, and ideally the rest should be in alphabetical order (though we may want to cut this from the scope depending on the level of complexity).
To navigate back to the table view from the entity-level view, we will use a back link above the summary (see: https://github.com/digital-land/submit/issues/406#issuecomment-2344033857).

As a data provider, when I'm on the dataset issues page, I see a table that shows me an aggregated view of all the records with the issue that I'm viewing.
As a data provider, when I'm on the dataset issues page, the table contains a link to each individual entity that takes me to the entity-level view.
As a data provider, when I'm on the entity-level view of the dataset issues page, I see a link to take me back to the table view.