feat(ui): add new themed table component

[yannisbarlas]

Related to #411.

Replaces the tables in the dashboard, as well as the table in /admin/manuscripts with a fresh ui that

• extends ant's table
• is accessible
• is typescript
• is much more straightforward and maintainable code-wise
• addresses some UX concerns with the existing tables (handling columns with large width, filtering and sorting options being visible, search matches clearly showing why they matched and more)

Some notes:

• There used to be a submit chevron column for table configs that added a small chevron arrow that took the user to the manuscript submission page. This was not used by any deployment and has been deleted.
• Rows on some of the tables were clickable. This has been dropped in favor of using the action links on the last column. The long term plan is to have all rows clickable and no actions column, but that's a separate discussion for a separate PR. For the time being, let's stay consistent and not have rows clickable on any of these tables.
• Searching now matches only data that is on the manuscript. It used to be the case that it also matched team members on the manuscript (e.g. a reviewer's name). This is not the case anymore. There is one migration in this PR that updates all manuscripts with the updated search data (since the search column is written on update, not on search).
• Title links and import (coar / semantic scholar) icons used to be tied to using the titleAndAbstract config option instead of submission.$title. Now they are independent. If there is an import source, the icon will be displayed. If there is a link in the title data, it will wrap the title in a link. using titleAndAbstract will add a clickable info icon that will reveal a preview of the abstract, like it did before. submission.$titleandtitleAndAbstract` will behave the same otherwise.
• • I updated badges app-wide to be consistent in shape and color.

Other notes that do not relate to tables:

• I added a bundle analyzer for the client (see analyze in package.json's scripts.
• I added a setup for the server tests that enables parallelism (each vitest worker will use a separate db) that drops the time it takes for the current tests from 80s to 30s.
• There's changes in the translation files. Deployments that override them will need to be updated.