[Security Solution] Bulk Editing UX Improvements

[banderror]

Related to: https://github.com/elastic/security-team/issues/1973 (internal)

Summary

This is a follow-up epic to the original one. As opposed to implementing various bulk editing actions, this epic focuses on bug fixes, performance improvements, and UX in general.

Sub-tasks

Bugs and edge cases

Preview Give feedback

1. [Security Solution] Bulk actions and Custom rules got disabled when custom user have "NONE" access of actions and connectors. #141050
   Feature:Rule Details Feature:Rule Management Team: SecuritySolution Team:Detection Rule Management Team:Detections and Resp bug impact:medium +7
2. [Security Solution]User is not able to add maximum value supported into Additional look-back time field. #142959
   Feature:Rule Management Team: SecuritySolution Team:Detection Rule Management Team:Detections and Resp bug impact:low +6
3. [Security Solution] Remaining bug in bulk editing index patterns of rules with a data view #138383
   Feature:Rule Management Team: SecuritySolution Team:Detection Rule Management Team:Detections and Resp bug impact:medium v8.4.0 +7

UX improvements

Preview Give feedback

1. [Security Solution] Custom index is not displayed when add or delete the index pattern under bulk actions #126046
   Feature:Rule Management Team: SecuritySolution Team:Detection Rule Management Team:Detections and Resp enhancement impact:medium v8.4.0 +7
2. [Security Solution] Improve the UI for showing results of bulk actions #146283
   Feature:Rule Management Team: SecuritySolution Team:Detection Rule Management Team:Detections and Resp enhancement needs design +6
3. Central management for the detection actions #80342
   Feature:Detection Rules Feature:Rule Management Team: SecuritySolution Team:Detection Rule Management Team:Detections and Resp Theme: TBD enhancement +7

Performance improvements

Preview Give feedback

1. Write a dev doc about the methodology of testing the performance of API endpoints. Describe things like test cases (data and permutations), statistical significance (how many "runs"/"measurements" to do per test case), load and parallelism (for example, 100 sequential requests + 100 requests in 20 chunks where 5 requests are parallel in each chunk), etc. Use this methodology consistently for future perf measurements.
2. Optimize the performance of API keys regeneration. Figure out how API keys work and what's encoded inside (username, privileges?) -- this would give us an understanding of the limitations and available options. Regenerate API keys in bulk. Use the same API key for all the rules that are being updated -- instead of generating N keys for N enabled rules. Reuse the existing API key if the same user updates a rule.
3. Remove the legacy actions migration logic from the _bulk_action endpoint
4. [RAM] add support of bulk update "muteAll" rule property in rulesClient #139084
   8.5 candidate Feature:Alerting/RulesManagement Feature:Rule Management Team: SecuritySolution Team:Detection Rule Management Team:Detections and Resp Team:ResponseOps performance +8
5. Implement a bulk get method in the RulesClient and use it from the _bulk_action endpoint
6. Implement a bulk create method in the RulesClient and use it from the _bulk_action endpoint
7. Implement a bulk delete method in the RulesClient and use it from the _bulk_action endpoint
8. Implement a bulk enable/disable method in the RulesClient and use it from the _bulk_action endpoint
9. Implement a bulk duplicate method in the RulesClient and use it from the _bulk_action endpoint (alternatively, could be solved with 2 methods: bulk get + bulk create)

Refactoring

Preview Give feedback

1. Find a proper place for the validation logic that ensures that prebuilt rules can't be created/updated/edited except from the addPrepackedRulesRoute. (comment)
2. Clean up the bulk actions route handler. Extract code into files, consolidate the implementation in a single place

[elasticmachine]

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