Akri DEV Helm Chart 0.8.12 - akri-opcua-discovery-daemonset Failure

[hemantkathuria]

Describe the bug
akri-opcua-discovery-daemonset - fails to discover the OPC UA server generates the following error.:

[2022-06-16T00:37:28Z INFO akri_opcua::discovery_impl] do_standard_discovery - for DiscoveryUrls ["opc.tcp://10.0.2.4:50000/"]
thread 'tokio-runtime-worker' panicked at 'Cannot drop a runtime in a context where blocking is not allowed. This happens when a runtime is dropped from within an asynchronous context.', /cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/blocking/shutdown.rs:51:21
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

After restarting the "akri-opcua-discovery-daemonset " it stucks at below and does not discover the server anymore.

[2022-06-16T01:00:00Z INFO opcua_discovery_handler] main - opcua discovery handler started
[2022-06-16T01:00:00Z TRACE akri_discovery_utils::discovery::discovery_handler] run_discovery_handler - registering with Agent with uds endpoint
[2022-06-16T01:00:00Z INFO akri_discovery_utils::registration_client] register_discovery_handler - entered
[2022-06-16T01:00:00Z INFO akri_discovery_utils::discovery::server] internal_run_discovery_server - entered

[kate-goldenring]

this is probably related to this PR that updated our opcua crate version: #479
While this is being investigated, I'd recommend adding --version 0.8.10 to installations of the akri-dev chart or use the latest release chart

[kate-goldenring]

We have encountered this issue locka99/opcua#148. I tried updating to latest where they added a little more async functionality. I will look into seeing if we can gracefully handle the errors instead.