[BUG] [FEATURE] Command confirmation for switches ModbusRTU and RTUoverTCP

[maufc]

Describe the bug
Modbus RTU and RTUoverTCP switches should wait for the response (confirmation) in order to confirm the new state of the switch.
The switch button should wait the response of the device. At this moment, if the command was not executed, the states changes until a new regular requests is make.
I found also that the commands can me send at the same time the regular requests are made making crossing modbus queries to the device.
The problem origin could come from this problem: #1148 waiting for a response.

To Reproduce
Just define a tag (coil status) of a modbus rtu connection and assign it as a property to a switch.
Go to Lab, and try to change the coil status with the switch.
See the app log and the port log.

Screenshots

Environment

• FUXA version: V.1.1.19-1587
• Node.js version: 16.16.0
• npm version: 8.11.0
• Platform/OS: Ubuntu 22.04
• Browser: Firefox 124.0.2 (64-bit)

[rvbatista]

ModbusRTU should be used for serial communication from the server, and RTUoverTCP should be used with serial device using transparent gateway. I have to check if there is some kind of mechanism to handle concurrent requests, but I think that neither Fuxa nor Modbus-serial have this. And it's kind of critical for serial devices.