Remove api key validation

[jackgerrits]

Why are these changes needed?

It's not our business to check if keys are valid. If they are invalid, OpenAI or the given provider will provide the appropriate error message. The alternative of checking keys means we will exist in this permanent state of chasing key format changes which is not necessary or helpful and people are getting confusing warning messages due to false positives.

Related issue number

Closes #3345
Closes #3157
Closes #3544

Replaces #3330
Replaces #3494

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.

[gitguardian]

⚠️ GitGuardian has uncovered 8 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
12853598	Triggered	Generic High Entropy Secret	ed2bec7	test/oai/test_utils.py	View secret
10404693	Triggered	Generic High Entropy Secret	ed2bec7	test/oai/test_utils.py	View secret
12853599	Triggered	Generic High Entropy Secret	ed2bec7	test/oai/test_utils.py	View secret
10404694	Triggered	Generic High Entropy Secret	ed2bec7	test/oai/test_utils.py	View secret
12853601	Triggered	Generic High Entropy Secret	ed2bec7	test/oai/test_utils.py	View secret
10404696	Triggered	Generic High Entropy Secret	ed2bec7	test/oai/test_utils.py	View secret
10422482	Triggered	Generic High Entropy Secret	ed2bec7	test/oai/test_utils.py	View secret
12853602	Triggered	Generic High Entropy Secret	ed2bec7	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.}

[nstielau]

+1, thanks @jackgerrits

There is a case for autogen owning an improved developer UX here, but without a PR on the table and continued errors, I think this is the right move.

Also, since OpenAPI doesn't provide any validation function or API, autogen will be chasing any changes that it seems OpenAI can and does make.

[robraux]

@jackgerrits

Looks like this check is broken if not isinstance(client, openai.AzureOpenAI) and str(client.base_url).startswith(OPEN_API_BASE_URL_PREFIX):

Don't you want the warning to only display if the instance IS the AzureOpenAI? I'm using main branch now and getting the warning for all of my standard OpenAI clients. Was this intended functionality to introduce?

[jackgerrits]

You're totally right, thanks for catching that!