AutoGen logging using Azure Cosmos DB

[wmwxwa]

Why are these changes needed?

Adding the connector to use Cosmos DB for logging

Related issue number

N/A

Checks

• [ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
• [ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
• [ ] I've made sure all auto checks have passed.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 34.28571% with 69 lines in your changes are missing coverage. Please review.

Project coverage is 30.48%. Comparing base (372ac1e) to head (508261f). Report is 18 commits behind head on main.

Files	Patch %	Lines
autogen/logger/cosmos_db_logger.py	37.34%	51 Missing and 1 partial :warning:
autogen/logger/logger_factory.py	23.07%	10 Missing :warning:
autogen/runtime_logging.py	0.00%	7 Missing :warning:

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2329      +/-   ##
==========================================
- Coverage   33.11%   30.48%   -2.64%     
==========================================
  Files          86       87       +1     
  Lines        9108     9340     +232     
  Branches     1938     2137     +199     
==========================================
- Hits         3016     2847     -169     
- Misses       5837     6158     +321     
- Partials      255      335      +80     

Flag	Coverage Δ
unittest	12.81% <34.28%> (?)
unittests	29.71% <34.28%> (-3.41%)	:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
10404693	Triggered	Generic High Entropy Secret	c1f0149c3e86fa115426d0e0078ee157f96da07d	test/oai/test_utils.py	View secret
10404662	Triggered	Generic CLI Secret	4797f1bc09294df6ed45681a2f98c7da591cb0c9	.github/workflows/dotnet-release.yml	View secret
10404694	Triggered	Generic High Entropy Secret	c1f0149c3e86fa115426d0e0078ee157f96da07d	test/oai/test_utils.py	View secret
10404696	Triggered	Generic High Entropy Secret	c1f0149c3e86fa115426d0e0078ee157f96da07d	test/oai/test_utils.py	View secret
10422482	Triggered	Generic High Entropy Secret	c1f0149c3e86fa115426d0e0078ee157f96da07d	test/oai/test_utils.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[wmwxwa]

• [ ] Add content on Azure Cosmos DB to https://github.com/microsoft/autogen/blob/main/notebook/agentchat_logging.ipynb

[wmwxwa]

• [ ] Install azure-cosmos package in workflow while debugging this PR and replace them with pytest.skipif after completion

[wmwxwa]

Cannot revolve conflict. Continuing the work under PR 2760

[Hk669]

@wmwxwa had come across an other PR #2760 . if that's the updated one. can this be closed?