fix(AutocompleteWidget): show actions

In the HTML stories, we're directly manipulating the DOM and using JavaScript to create and interact with widgets. When we define selectionChangedEvent as a function that does nothing (() => {return;}), we're essentially providing a placeholder for the event handler. This is necessary because the HTML widget expects a function to be passed as the selectionChangedEvent handler. If we don't provide a function, the widget might not initialize correctly or might not behave as expected when an event occurs.

In contrast, React stories are more integrated with Storybook's React environment, which includes support for actions. When we define an action in the story's argTypes, Storybook automatically creates a function that logs the event to the Storybook UI. This is why we don't need to explicitly define selectionChangedEvent as a function in the React stories. Instead, we define it in argTypes like so:

argTypes: {
 selectionChangedEvent: { action: 'selectionChangedEvent' },
},

This tells Storybook to create an action for selectionChangedEvent, which will be called with the event data whenever the event occurs in the component. This is a feature of Storybook's React environment and is not applicable to plain HTML widgets.

I separated AutocompleteWidgetStoryArgs (providing the function) and AutocompleteWidgetStoryArgsReact (not providing a function) and passed them to the corresponding HTML and React stories.

ts4nfdi / terminology-service-suite

fix(AutocompleteWidget): show actions #77