Memory Reference Leak from Create client node

[KishorKumar2222]

Running the create client node is showing some unknown memory reference leak in desktop execution trace toolkit

AB#2844161

[jasonmreding]

I'm not sure what DETT tracks for leaks or how it tracks them, but I suspect this might be caused by the cleanup proc that gets registered. In this case, the cleanup proc calls DeregisterCleanupProc, but it doesn't call UnregisterPointer. This leaks the smart pointer which in turn prevents the underlying grpc channel from being cleaned up. However, that should only be an issue if the code doesn't explicitly close sessions and instead relies on LV to automatically cleanup references when the VI goes idle.