Enable multi-select capabilities in Perses table panels, allowing users to select one or more rows and perform predefined actions (e.g., Delete VMs, Stop VMs, Restart VMs). When an action is selected, the selected row data should be sent to a configurable endpoint (e.g., Ansible, webhook) to trigger automation workflows.

Actions will be defined in the panel configuration and should include:

• Action ID and display name

• Target endpoint URL

• HTTP method (e.g., POST)

• Optional payload template using selected rows as input

If no actions are configured, the multi-select UI (checkboxes and action dropdown) should not be displayed.

This feature will support streamlined day-2  by enabling bulk actions directly from the dashboard.

Definition of Done for Engineering Story Owner (Checklist)

 * ...

Development Complete

 * The code is complete.
 * Functionality is working.
 * Any required downstream Docker file changes are made.

Tests Automated

 * [ ] Unit/function tests have been automated and incorporated into the
build.
 * [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

 * [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

 * [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

[https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby]]),

and ensure doc acceptance criteria is met.
 * Call out this sentence as it's own action:

 * [ ] Link the development issue to the doc issue.

Support Readiness

 * [ ] The must-gather script has been updated.