* Add ETW support in zap logger for CNI
Added a zap WriteSyncer to enable direct ETW logging through zap core, maintaining existing logging structure while to ETW from CNI.
* Transform 'zapetw' package into a standalone module for external use
* Revert "Transform 'zapetw' package into a standalone module for external use"
This reverts commit 63050ed68d353e43ae1b1fedd11b8e99259b7a28.
* Relocate EtwWriteSyncer.go to zapetw module for improved organization
- Renamed and moved cni/log/ETWZapCore/EtwWriteSyncer.go to zapetw/write_syncer.go.
* Applied gofumpt formatting to adhere to style guidelines.
* 1. Implemented platform-specific ETW logging enhancements.
2. Refactor ETW initialization into dedicated method and zapetw package.
* Changed InitETWLogger method signature for Linux.
* Wrapped error messages at each level of the call hierarchy.
* Removed punctuation marks from error messages.
* Wrapped error messages with errors.wrap method.
* Added comments for clarity.
* implemented zap.core for ETW.
* Fixed lint issues.
* Catch errors from etw.writeEvent method.
* Renamed provider.
* Abstracted etw core creation in logger_windows.
Removed unsupported error from logger_linux to keep the behaviour uniform.
* renamed unused parameter.
* Renamed variable to lower camel case as it is private. Removed additional local reference.
* fixed variable name.
* Added comment.
* Renamed ETW provider, removed application names from the provider name.
---------
Co-authored-by: Sivakami Subramaniam <t-sivakamis@microsoft.com>
1eed84ef61