Description

This PR

• removes code related to the export widget feature
• add the plug for the non-enterprise users with a promotion of the new feature

• do the groundwork for the enterprise plugin to be able to use this exporting feature there

Using our plugin system faces a couple of problems:

• We already have actions from enterprise (fe switch to log view action) that we place into the dropdown menu and now we have to add them into the menu as well. We would like to keep only already existing views.widgets.actions. To be able to separate actions by position we extend WidgetActionType. Now it has a prop position where we can define where exactly we would like to render it. We also add new component props there. We use it instead of action and title to render the action component. So now we can use action and title OR component props to render
  action.

• we have to keep exporting for the messages widget. We add export messages action component into our plugins views.widgets.actions in the core.

• and we have to add the plug only for the non-enterprise users. To do that we provide ExportWidgetAction with position menu and ExportWidgetActionDelegate as a component. ExportWidgetActionDelegate looks at views.components.widgets.exportAction entity. If there is no component to render it renders a plug

Motivation and Context

fix: #19339

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (non-breaking change)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.

/jenkins-pr-deps https://github.com/Graylog2/graylog-plugin-enterprise/pull/7273