[RAM] add support of bulk update "muteAll" rule property in rulesClient

[vitaliidm]

Describe the feature:
Add support of bulk update "muteAll" rule property in rulesClient

Describe a specific use case for the feature:
To add/update rule actions on Security Solution side, we need an ability to update muteAll rule property in bulk.
It needed for cases:

• when throttle set to no_actions, but rule was unmuted
• when throttle set to some value, but previously rule was muted

Reference in code:
https://github.com/elastic/kibana/blob/8.4/x-pack/plugins/security_solution/server/lib/detection_engine/rules/utils.ts#L122-L147

Proposals of implementation

1. Add a new operation to rulesClient bulkEdit method
   Proposed new operation would look like:

{
      operation: 'set';
      field: Extract<BulkEditFields, 'muteAll'>;
      value: Rule['muteAll'];
};

Also, we will need to address some additional logic, that exists in current muteAll/unmuteAll methods

• cleanup of additional properties in rule

      ...
      mutedInstanceIds: [],
      snoozeSchedule: clearUnscheduledSnooze(attributes),
      ...

• check rule actions authorization:

     if (attributes.actions.length) {
       await this.actionsAuthorization.ensureAuthorized('execute');
     }

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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

[XavierM]

@vitaliidm, we think that this #139742 will allow you to create bulk snooze with out problem. And we will also hope that this #137430 will allow your users to take advantage of the new snooze functionality that we created.

[vitaliidm]

@XavierM
Thanks for the update.

we think that this #139742 will allow you to create bulk snooze with out problem.

Looks like functionality in this PR would allow to set/unset muteAll 👍

[cnasikas]

Hey @vitaliidm! It seems that the functionality added in #139742 allows to set/unset muteAll. Should we close the issue?

[vitaliidm]

@cnasikas , Yes I think it can be closed
mute/unmute logic was changed in #147736, so this one not needed anynore