Currently the Detections Bulk Actions are tightly coupled to the Rules Table. This includes using custom bulk* hooks to return event handlers, UI visibility flags, and more that are then managed and forwarded along by the Rules Table:

Where possible, we should extract functionality into the desired context's interface (encapsulating any relevant actions/state), and then inject the necessary bulk actions depending on the context (installed rules table will get all the bulk actions we know and love, whereas upgrade/new rules tables will get installed/resolve conflicts/etc actions).