Blog post for enhanced non-OpenAI model support

[marklysze]

PR for blog post for the enhanced support of non-OpenAI models through new client classes. Includes Anthropic, Mistral.AI, Together.AI so far.

Related issue number

See Roadmap issue #2946

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.

[marklysze]

Thanks @olgavrou, I'll put the function calling in and would like to write some text around using these alternative models including some tips/parameters that are useful to tweak and work with. That will take a day or two to do. Hope that's okay.

There is also a dependency on the next release, which will include these new client classes, v0.2.30. #2946

[marklysze]

I've updated with the upfront text. Still to do is the function calling example which I'll work on next.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [11616921](https://dashboard.gitguardian.com/workspace/221093/incidents/11616921?occurrence=148427220) | Triggered | Generic High Entropy Secret | 0f33e846a7581491d2901eebaa331cc2f6f86f7e | notebook/agentchat_agentops.ipynb | [View secret](https://github.com/microsoft/autogen/commit/0f33e846a7581491d2901eebaa331cc2f6f86f7e#diff-b63f23e062ab79e05d69e5d7ff31ab62e29d958237ef1807891be38056d2b90dL107) |

🛠 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 secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.}

[marklysze]

Thanks @olgavrou and @qingyun-wu, I've added the function calling to the blog post. Have also added a separate notebook for more function calling between different providers (separated it as it was very long).

Let us know what you think and if we can improve it.

[marklysze]

Thanks for approving @olgavrou!

@qingyun-wu, let us know if you would like anyone else to review or if you want any changes. Groq has been added since it is now merged.

[Hk669]

@olgavrou @qingyun-wu are we waiting for all the non-OpenAI models to be merged? can you please review this blog and let us know if you would like anyone else to review or if you want any changes.