[ResponseOps][Alerts] Move the alerts table into a dedicated package

[umbopepato]

Current state

The alerts table API was updated in #194978 to remove the registry and only rely on props-based configuration options. Usages of the table across Kibana were updated accordingly without implementing any architectural changes.

Goal

Check the converted usages with solutions (they can contribute to the feature branch if needed), fix tests and finish migrating the table code to a dedicated package.

Tasks

Preview Give feedback

1. Remove the alerts table registry ([ResponseOps][Alerts] Remove the alerts table registry #194978)
2. Move the alerts table code to a dedicated package (and generic dependencies to other relevant ResOps packages) ([ResponseOps][Alerts] Move alerts table to package #201547)
3. Fix failing tests
4. Add a configuration option to the Cases SDK to provide different tables/table configurations in each solution (i.e. pass the table component as a prop to CasesContext) ([ResponseOps][Alerts] Add configuration option for alerts table to getCases #207038)
5. Find a replacement for the toggleColumn action that Security Solution extracted from the alerts table registry (temporary solution [ResponseOps][Alerts] Fix alerts table column toggling not working from security flyout #208052)
6. Check with solutions the converted usages of the table (reviews in [ResponseOps][Alerts] Move the alerts table to a dedicated package #207878)

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)