[FEATURE] add support for row actions on table plugins

[jgbernalp]

Description

This PR adds a new SelectionAction feature. perses/perses#3788. This allows to define actions based on selected data, for example calling an HTTP request with the interpolated data from multiple rows selections.

A new SelectionContext was added so the Panel plugins can share the selected data with the Panel header, which contains the selection actions as part of the, already implemented, header actions. If select actions are defined in the plugin spec, a ⚡ will be added to the header actions and for tables, checkboxes will be added to rows. The provider is passed in the plugin initialization using a factory, in the future this will allow other plugins to use selections to trigger actions, for example selecting a point in a line chart to send it to an LLM to ask questions about the data.

Screenshots

Checklist

• Pull request has a descriptive title and context useful to a reviewer.
• Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
  following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
• All commits have DCO signoffs.

UI Changes

• Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
• Code follows the UI guidelines.
• E2E tests are stable and unlikely to be flaky.
  See e2e docs for more details. Common issues include:
  • Is the data inconsistent? You need to mock API requests.
  • Does the time change? You need to use consistent time values or mock time utilities.
  • Does it have loading states? You need to wait for loading to complete.