Help users to get started with access to public opcua servers

[jfhenon]

To help users to test quickly OIBus, we could define a minimal working configuration for the south, it could be OPCUA (a list is available here
https://github.com/node-opcua/node-opcua/wiki/publicly-available-OPC-UA-Servers-and-Clients)
We need to decide for the North side (actually a simple Web console screen similar to the console could be an addition)

[burgerni10]

Here is what I propose:

1. Add a firstStart flag (boolean) for the whole configuration. At first, the flag is set to true, and when a new connector is added, the flag is set to false.
2. When the flag is set to true, display a button on the front main page to active a quick start.
3. The quick start add three connectors :
   -Console Quick Start (North Connector)
   -OPCUA Quick Start (South Connector) with
   -url: opc.tcp://uademo.prosysopc.com:53530/OPCUA/SimulationServer
   -points: to be determined
   -MQTT Quick Start (South Connector) with :
   -url: mqtt://broker.mqttdashboard.com:1883
   -points: testtopic/#

For some connectors like MQTT or OPCUA, a firstStart flag for these connectors can be added in the configuration file. The flag is set to true when the connector is new. When true, a quick start button is displayed. when clicked, it set the configuration of this connector to the values described before.

We have to warn the user to check the firewall rules somehow, and to be careful that the MQTT broker or OPCUA server are still available

[burgerni10]

Looking back at my previous comment, we can have something simpler and probably better for the user experience :
When adding a new connector, we can add a connector from scratch, or add it from a template. If a connector has no template, the user won't have to choose and will directly add a connector from scratch.
I think the "NewDataSourceRow" and "NewApplicationRow" can manage that.
The config templates of each connector can be added in the config folder (beside the defaultConfig file)