Replace config actions with Thing actions

[florian-h05]

With UI support for Thing actions in openHAB 4.3, I would like to get rid of the config actions, which have a high code complexity in the UI and as the issues with Z-Wave's config actions have shown, are prone to bugs.
Bindings should implement Thing actions instead of using this hacky approach-

The following search query gives an overview of the remaining config actions:
https://github.com/search?q=org%3Aopenhab+name%3D%22actions%22+language%3AXML&type=code&l=XML

Affected bindings are:

• Konnected
• Max
• MQTT HomeAssistant
• Z-Wave

Pinging @openhab/add-ons-maintainers and @openhab/z-wave-maintainers, as well as @ccutrer for MQTT HomeAssistant.

[ccutrer]

:nod:. For Home Assistant, it's the Update component. I've been meaning to figure out Thing actions anyway so I can add the Siren component, which doesn't clearly map to any channel since it almost always take additional parameters to the "trigger" action.

[ccutrer]

So I started work on this, but have run into the problem that the BaseThingHandlerFactory registers ThingHandlerServices immediately after the ThingHandler has been created, but before the ThingHandler has been initialized. I want to expose actions dynamically for the highly dynamic things that MQTT Home Assistant manages, depending on if it has an Update component or not (and in the future, other specific component types that I want to create actions for). @openhab/core-maintainers: would you be opposed to adding a method to BaseThingHandlerFactory to dynamically register new services for a ThingHandler at any time (when the ThingHandler has detected that a service is relevant)?