Updating OPCUA server better mimick the Powerfuse OPCUA server. Allows accessing nodes and values in the same manner

- Add buildout.hash.cfg
- Include instance-input-schema.json describing (contains a description of the parameters) and instance-output-schema.json
- Introduce instance.cfg.in and instance-opcua.jinja.cfg.in
- Enable parameterized instance requests with nested JSON support
- software.cfg.json with software-type - default
- opcua-to-http-gw.py with OPCUA sever/client, login and data polling functionality.
- Note: Functionality incomplete due to missing asyncua dependency

This commit lays the groundwork for more flexible instance configuration. However, it's not yet
functional without the asyncua library.

- Lacking the ability to request nested json files.
- Missing asyncua hence not working

- Lacking the ability to request nested json files.
- Missing asyncua hence not working

- Add login to OPC UA server via credentials
- Establish interval connection for reading nodes from OPC UA server
- Implement monitoring function to subscribe and monitor data changes on OPC UA server nodes
feat: Implement server functionality hosting data and randomly chaning it (minimal-server.py)

Adding via jinja2 default paramters for instance-parameters. Adding the functionality to parse parameters via request

    Adding via jinja2 default paramters for instance-parameters. Adding the functionality to parse parameters via request

Adding via jinja2 default paramters for instance-parameters. Adding the functionality to parse parameters via request

from cryptography = 3.3.2 to cryptography = 42.0.7 as asyncua 1.1.0 requres version >40.0.1

Updating asyncua = 0.9.2 to asyncua = 1.1.0 as this resulted in asyncua.ua.uaerrors._auto.BadNoMatch: "The requested operation has no match to return."(BadNoMatch). 

Updating asyncua = 0.9.2 to asyncua = 1.1.0 as this resulted in asyncua.ua.uaerrors._auto.BadNoMatch: "The requested operation has no match to return."(BadNoMatch).