Initial support for Algodue UEM meters on CP0 and CP1 and as EVU-Kit

[dj3mu]

This commit adds support for Algodue UEM meters at internal chargepoints.
Tested with a modified openWB2 and a UEM80-4D R (Modbus RTU version).

Modbus Address is set to 155 for CP0 and 156 for CP1. Please adjust if does not fit the openWB adressing concepts (which I don't know).

Support for UEM80-4D E as EVU-Kit is also included. But necessary UI changes are not yet part of this PR.

[benderl]

Danke für das neue Zähler-Modul.
Bitte noch ein paar Anpassungen vornehmen, dann können wir das so integrieren.

[benderl]

Same registers should be valid for Ethernet/Modbus-TCP models (e.g. UEM80-4D E). But since, according to my reverse-engineering of the code, ability to configure EVU Kit to use it requires UI changes and is generally more complex, I was not yet able to integrate that. Additionally the problem is that EVU-Kit has hard-coded Modbus-TCP Port numberr of 8899 but Algodue meter's Modbus Port is the standard-port 502 and cannot be changed.

Maybe it can more easily be integrated with an openWB-Flex-Kit. Hints are welcome. But it could also be integrated in a second pull request.

The "EVU-Kit" always consists of a Modbus/TCP to RTU converter and one or more Modbus/RTU devices. So implementing the Modbus/TCP models as another option of the kit would break this sheme.

The Modbus/TCP models could be im plemented by a modified "carlo_gavazzi" device and counter component.
https://github.com/openWB/core/tree/master/packages/modules/devices/carlo_gavazzi/carlo_gavazzi

Integration into the settings ui should also be straight forward. Please let me know if you have questions.
https://github.com/openWB/openwb-ui-settings/tree/main/src/components/devices/carlo_gavazzi/carlo_gavazzi

[dj3mu]

I've accepted all suggestions and added the EVU-Kit code for Algodue as instructed above.

UI changes in openWB/openwb-ui-settings#582

Unfortunately I have never done and have absolutely no toolchain for Web-Development.
So I've no idea how to transpile and test-wise deploy UI to openWB. Hence I also can't really test the Modbus-TCP device driver yet.

I'd propose to handle the above PR for UI and merge it together with this PR.
I'll then, if not yet working out-of-the-box, create a new PR with the integration fixes.

[LKuemmel]

waiting for feedback for reset functionality of the network connection