[FEATURE] add header and row actions to table

[jgbernalp]

Description

This PR adds the selection actions to the table

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.

[shahrokni]

I am just curious how it works. Actually as a user I am still confused how should I work with this feature.
It reminds me of the custom event of JS. Should I be able to define the event handler here? How? Somehow I should be able to handle the event when it is dispatched.

[jgbernalp]

I am just curious how it works. Actually as a user I am still confused how should I work with this feature. It reminds me of the custom event of JS. Should I be able to define the event handler here? How? Some how I should be able to handle the event when it is dispatched.

Yes, this is a custom JS event. This could be provided by any other plugins, embedded UIs, or the Perses UI by registering event callbacks. But this is just the trigger of a generic action, the action implementation depends on whoever implements the handler.

[shahrokni]

I am just curious how it works. Actually as a user I am still confused how should I work with this feature. It reminds me of the custom event of JS. Should I be able to define the event handler here? How? Some how I should be able to handle the event when it is dispatched.

Yes, this is a custom JS event. This could be provided by any other plugins, embedded UIs, or the Perses UI by registering event callbacks. But this is just the trigger of a generic action, the action implementation depends on whoever implements the handler.

Hmm, I see. OK, cool!