Update krabsetw commit

[sid-dahiya]

There are vulnerabilities in the nuget packages from krabsetw submodule. This change is moving the commit forward to try and fix the issue.

The error we are seeing in our pipeline:

Starting Multifeed Nuget Security Analysis: 
third_party/cpp_client_telemetry/third_party/krabsetw/Microsoft.O365.Security.Native.ETW/.nuget/NuGet.Config - Missing <clear/> statement.
third_party/cpp_client_telemetry/third_party/krabsetw/krabs/.nuget/NuGet.Config - Missing <clear/> statement.
Starting Multifeed Python Security Analysis: 
Starting CFS NuGet Analysis: 
third_party/cpp_client_telemetry/third_party/krabsetw/Microsoft.O365.Security.Native.ETW/.nuget/NuGet.Config - External feeds found in the file.
third_party/cpp_client_telemetry/third_party/krabsetw/krabs/.nuget/NuGet.Config - External feeds found in the file.
Starting CFS NPM Analysis: 
Azure Artifacts Configuration Analysis found 2 vulnerable NuGet package manifests in the repository. Visit http://aka.ms/azure-artifacts-configuration-analysis for more details.

[maxgolov]

Just a bit of history: I added this originally for some ETW work / test cases. Ideally I would recommend you to maybe get rid of that submodule entirely in the long run.... OpenTelemetry ETW exporter didn't need that code. And to test the receiving end of ETW events, e.g. for Unit Tests, etc. - it's easier to use C# receiver. I remember facing some limitations in KrabsETW, that ultimately C# receiver was better. Also for manual testing - Visual Studio 2019+ has a built-in ETW viewer right now.

This page covers some alternatives that do not require KrabsETW:
https://github.com/open-telemetry/opentelemetry-cpp/tree/main/exporters/etw

[sid-dahiya]

Just a bit of history: I added this originally for some ETW work / test cases. Ideally I would recommend you to maybe get rid of that submodule entirely. OpenTelemetry ETW exporter didn't need that code. And to test the receiving end of ETW events, e.g. for Unit Tests, etc. - it's easier to use C# receiver. I remember facing some limitations in KrabsETW, that ultimately C# receiver was better. Also for manual testing - Visual Studio 2019+ has a built-in ETW viewer right now.

I think I might have to remove it. The module is introducing a .config file with its own dedicated nuget path and that's not supported in a lot of scenarios now.