[Security Solution] Improve bulk action executor

[maximpn]

Relates to: #139897

Summary

Current bulk action executor violates single responsibility principle so that it blocks concise feature development.

Details

While working on #139897 I've discovered that bulk action executor function violates single responsibility principle which makes it harder to extend its functionality by composition. The major part of the input parameters are optional and related to some of the actions. It makes it harder to use TypeScript guarding against passing unrelated parameters and requires good understanding of the function internals before its usage.

Obviously there is a room for improvement here. It can be achieved by splitting the logic by responsibility and improve typings. Decisions about the next steps like on success or on error should be done by the driver code. Taking that into account there are two ways

• split the executor into action executors

type BulkSearchParams = { query: string } | { ids: string[] };

async function executeRulesBulkAction(searchParams: BulkSearchParams): Promise<BulkActionResponse> {...}

async function executeRulesEditBulkAction(searchParams: BulkSearchParams, payload: BulkActionEditPayload[]): Promise<BulkActionResponse> {...}

async function executeRulesExportBulkAction(searchParams: BulkSearchParams): Promise<Blob> {...}

• split actions by type

type BulkSearchParams = { query: string } | { ids: string[] };
type BulkAction = {
  action: BulkAction.enable | BulkAction.disable | BulkAction.delete | BulkAction.duplicate | BulkAction.export;
  search: BulkSearchParams;
} | {
  action: BulkAction.edit;
  search: BulkSearchParams;
  payload: BulkActionEditPayload[];
}

async function executeRulesBulkAction<T extends BulkAction>(action: BulkAction): Promise<T extends 
 BulkAction.export ? Blob : BulkActionResponse> {...}

To handle errors and perform any other actions it's enough to wrap a function from above to try/catch/finally or create a reusable wrapper function. Unspecified arguments should be used by the driver code.

defaultSuccessHandler and defaultErrorHandler should be split into pure message generator functions to be exported separately and used by the driver code.

[elasticmachine]

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

[elasticmachine]

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