[Feature]: Add Connector for Modbus TCP

Is your feature request related to a problem? Please describe.

Within our manufacturing company we have different protocols on the Shop-Floor like Modbus TCP. Right now Azure IoT Operations does not have a connector for Modbus TCP. Since our manufacturing engineers could use the Azure IoT Operations UI to connect more machines, we would like to see a Modbus TCP connector, which would help to get the high frequency data in the Azure Cloud in a harmonized way and protocol.

Describe the solution you'd like

We would like to see a new microsoft-managed connector for Modbus TCP to MQTT. Configuration is managed via UI and stored via K8s CRD-Object. Within the Azure IoT Operations UI we can see the status, e.g. "active".

Connection Settings:

IP Adress or Hostname
Port, default is 502
Unit ID, default is 255 if connecting to a "bridge device"

Like OPC-UA has the concept of NodeIDs, there is a similar concept in Modbus TCP. It would take the following arguments:

Function Code (see https://ozeki.hu/p_5873-modbus-function-codes.html) FC1: Read Multiple Coils FC3: Read Multiple Holding Registers FC4: Read Multiple Input Registers FC6: Write Single Holding Registers FC15: Write Multiple Coils FC16: Write Multiple Holding Registers FC23: Read/Write multiple Holding Registers
Register adress, e.g. 4004
Quantity of Registers, e.g. 1
Data Type Word Double Real Float Integer Long Boolean Unsigned Integer, is the default
The Polling interval in ms

Additional documentation about Modbus TCP can be found here: https://ozeki.hu/attachments/5874/Modbus_TCP_IP_Implementation.pdf

Proposed implementation details (optional)

https://github.com/biancoroyal/node-red-contrib-modbus https://flows.nodered.org/node/node-red-contrib-modbus https://github.com/zgwit/modbus-mqtt-golang/blob/main/mqtt.go https://flows.nodered.org/search?term=modbus https://github.com/bitpool/edge-modbus/blob/master/core/modbus-client-core.js

Azure / azure-iot-operations