Add Bulk Selection and Bulk Change Criticality Feature to DataGrid

[opauloh]

Motivation

To enhance efficiency in managing assets, the DataGrid should support bulk selection of assets and provide the ability to change the criticality of selected assets. This feature allows users to manage multiple assets simultaneously, improving their workflow and reducing repetitive actions.

Definition of Done

• [ ] Add a checkbox to the DataGrid header for selecting all items on the current page.
  • Clicking the header checkbox should:
  • Select all documents displayed on the current page.
  • Check the checkboxes of all rows in the current page.
  • Ensure clicking on individual row checkboxes updates the selection status of the header checkbox.
• [ ] Implement a context action bar that appears when any assets are selected, showing:
  • "X assets selected": A dynamic text showing the number of selected assets.
  • Clicking on this text should open the Change Asset Criticality Flyout, allowing users to update the criticality of all selected items in bulk.
  • "Select all X assets": A button to select all items across all pages of the DataGrid.
  • The total count of selectable assets should be displayed in the button text (e.g., "Select all 500 assets").
  • Ensure the button toggles between selecting all assets and deselecting all assets.
• [ ] Implement bulk actions in the Change Asset Criticality Flyout to:
  • Display the current criticality for selected assets.
  • Allow updating the criticality for all selected assets.
  • Provide success or error notifications for the operation.
• [ ] Add unit tests to verify the functionality.
• [ ] Add integration tests to ensure:
  • Interaction between the DataGrid and the Change Asset Criticality Flyout works as expected.
  • The "Select all X assets" button selects/deselects all items correctly across pages.

Requirements

• The DataGrid should display feedback for slow operations when handling large selections (e.g., a loading spinner or progress indicator).

Out of Scope

• Changes to the backend logic for fetching or updating asset criticality (assumes API already supports bulk updates).
• Additional bulk actions beyond changing criticality.

Related tasks/epics

• https://github.com/elastic/security-team/issues/11247
• https://github.com/elastic/security-team/issues/10345

[elasticmachine]

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)