Build the TCP Listener application to run as a Windows Service

Currently the TCP Listener application runs as a user program, that is, to maintain its operation, the user must stay logged in the machine. The app would terminate once the user logged out. This is a major limitation because customer normally needs the app to run continuously for days, months or longer.

Below are the requirements previously proposed by Extensions team.

1. The TCP Listener Service can be deployed on any Microsoft Windows Server (2019 or later) with only the Common Service required for logging purposes.

2. The listening interfaces will be available on startup of the TCP Listener Service.

3. Functionality to be delivered as MSI installable on Enterprise SCADA 2021 or later.

4. It shall be possible to specify a debug level for the TCP Listener Service and to
   modify the debug level without restarting the TCP Listener Service (possibly via
   modifications to a .config.xml file separate from the main TCP Listener configuration file).

5. Existing TCP Listener functionality to be preserved, including:
   1) The TCP Listener Service will allow multiple connections (interfaces) to operate
   simultaneously.

2) The TCP Listener Service will use the same configuration file for Interface config as the existing TCP Listener stand-alone application.

Customers would welcome the new feature. The app had been used by quite a few customers since it was developed many years ago.

This would make the feature more user friendly in installation, version tracking and operation.