[FEATURE] Selection provider and Item actions

[jgbernalp]

Description

This PR adds a new Actions and selection features. 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 selection.

Two new Providers were added to the main Panel component, yes we have more providers but users don't have to configure these two, plugin developers can just use the hooks without any issue as they are resilient to undefined context:

• SelectionContext: allows to share the selected items between the plugin panel and the panel header. This will allow in the future to use selections from time series or other panel plugins.
• ItemActionsContext: allows to execute the actions configured in the plugin spec, either from the table row or the panel header.

I split into 3 commits so is easier to review:

1. b33ab5d adds the selection provider, adding a selection configuration option to common cue package
2. 43747e2 Improves the interpolation formats and moves the functions to the components package, re exporting in plugins for backwards compatibility
3. Adds the item actions provider, connecting the selections and actions, adds an actions configuration option to common cue package. The actions and selections integration was added to the table component for plugins to use. Other plugin integrations will follow.

Screenshots

Screen.Recording.2026-01-23.at.20.41.34.mov

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.