[Security Solution] Decouple Detections Bulk Actions from Rules Table

[spong]

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:

kibana/x-pack/plugins/security_solution/public/detection_engine/rule_management_ui/components/rules_table/rules_tables.tsx

Lines 101 to 134 in 598b18c

	const {
	bulkActionsDryRunResult,
	bulkAction,
	isBulkActionConfirmationVisible,
	showBulkActionConfirmation,
	cancelBulkActionConfirmation,
	approveBulkActionConfirmation,
	} = useBulkActionsConfirmation();
	const {
	isBulkDuplicateConfirmationVisible,
	showBulkDuplicateConfirmation,
	cancelRuleDuplication,
	confirmRuleDuplication,
	} = useBulkDuplicateExceptionsConfirmation();
	const {
	bulkEditActionType,
	isBulkEditFlyoutVisible,
	handleBulkEditFormConfirm,
	handleBulkEditFormCancel,
	completeBulkEditForm,
	} = useBulkEditFormFlyout();
	const { isBulkActionsDryRunLoading, executeBulkActionsDryRun } = useBulkActionsDryRun();
	const getBulkItemsPopoverContent = useBulkActions({
	filterOptions,
	confirmDeletion,
	showBulkActionConfirmation,
	showBulkDuplicateConfirmation,
	completeBulkEditForm,
	executeBulkActionsDryRun,
	});

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).

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)