Refactor of category-select-table component

[jarmoza]

Newly refactored category select table on the categorization page...

1. has required input (categories, categoryClasses) directly from the store
2. former instructions and title props have also been removed, relegated to the new refactored categorization page that will act more like a layout.
3. selectedCategory is still emitted to the categorization page (which maintains a currentCategory field to share between the category-select-table and the column-linking-table)

The component test...

1. Mocks store required input via getters
2. Runs through selection of all the default categories.
3. Spies for the emitted selected category output

[surchs]

Hey @jarmoza: really cool PR 🎉 and a very good size of changes and unit of work! This is great!
I checked it out, confirmed it works. I do have two comments:

1. A minor one about state keeping -> I think whoever holds state for currentCategory, it should only be in one place (see detailed comments inline)
2. More important: the tests should be as simple as we can, and only concerned with the component. So I'd say: let's get rid of the store methods and unused state variables and just write explicitly what the getters will give to the component at runtime (again, more detail in comments).

[jarmoza]

@surchs I believe with these last two commits, we are good to rebase this PR with https://github.com/neurobagel/annotation_tool/tree/dev_components_talk_to_store_directly

[surchs]

Awesome, @jarmoza. Yes, fully agreed. This is ready to be squashed into the dev branch! 🎉