Log analysis tool

[lmolkova]

AMQP SDKs issue investigation depends heavily on log parsing.
In the long-term, we should rely more on tracing, metrics, and logs being available in users APM tools and user being able to investigate simple issues without SDK's team help.
In the meantime, to analyze existing logs including perf runs, we can build a log analysis tool parsing and sending structured logs to Kusto/Log analytics to be able to query them and automate analysis on top.

Prototype: https://github.com/lmolkova/azure-sdk-log-parser

Related to #25114
TODO:

• switch to new logging format Structured logging with ClientLogger #25247
• We should also investigate how it's done in other languages and see if the tool can be reused
  • Go SDKs: use detailed 3rd party library logs
  • .NET SDKs: have comprehensive EventSource -> ILogger bridge with context and ability to export anywhere
  • JS: writes to stdout, can be customized to write anywhere, does not support structured logging
  • Python: uses Python logging library, it supports structured logging out of the box (with extra args )