fix(binding-opcua) fix binding-opcua

[erossignon]

• improve test
• refactor to 0.8.0 api
• improve typescript compliance (avoid using any)
• fix resource leaks
• properly terminate servr
• prevent too many subscriptions to be created.
• do not use opaque nodeIds (I.e ns=1;b=ABCDFE) anymore => to prevent clash with breaking changes in [email protected]

[relu91]

Thank you for your contribution to opc-ua implementation! About the stop method, I agree it should be async, it is something that we need to fix.

[danielpeintner]

Unfortunately we do have test issues with OPCUA now, see

https://github.com/danielpeintner/thingweb.node-wot/runs/3732161234?check_suite_focus=true

@erossignon do you have an idea what is causing this issues?

[erossignon]

@erossignon do you have an idea what is causing these issues?

On some slow VM, the data change monitoring events are not guaranteed to be sent by the server one after the other.
This causes some flaky behavior, I have created a PR to take this into account.