NMR test to track deregistering of client or provider

This issue is the follow up of [issue 2048](https://github.com/microsoft/ebpf-for-windows/issues/2048)
Deregistration of client / or provider  ( which is different from registration failing) and this mock needs to implemented in which needs to implemented in nmr::bind which most likely needs to be implemented in kernel tests.
ClientAttachProvider -> NmrClientAttachProvider -> ProviderAttachClient – and after this provider either of the client or provider detaches. In which case NMR calls detach callbacks on both client and provider. The mock NMR implementation for this (_nmr::bind) is NOT doing this. So this is one change we can take in mock NMR. But for testing this, we have to run threads in parallel which will call ebpf_provider_load/unload and ebpf_extension_load/unload in parallel.

Start with the mock NMR implementation in nmr::bind and the kernel tests that exercise ClientAttachProvider, NmrClientAttachProvider, and ProviderAttachClient. Trace provider and client attach and detach callbacks, then run parallel provider and extension load/unload operations. Done means the mock invokes both detach callbacks and the NMR test covers deregistration during concurrent operations.

Written by the indexing model from the issue text.