support openai 'sk-proj-' apikey format

[saberuster]

Why are these changes needed?

I recently created a new oai api key and found that it has 'sk-proj-' as the prefix, and the current code base can only match the 'sk-' prefix.

autogen/autogen/oai/openai_utils.py

Line 93 in d307818

api_key_re = re.compile(r"^sk-[A-Za-z0-9]{32,}$")

Related issue number

Checks

• [ x ] 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.
• [ x ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
• [ x ] I've made sure all auto checks have passed.

[gitguardian]

⚠️ GitGuardian has uncovered 4 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
-		Generic High Entropy Secret	ef77502	test/oai/test_utils.py	View secret
-		Generic High Entropy Secret	ef77502	test/oai/test_utils.py	View secret
-		Generic High Entropy Secret	ef77502	test/oai/test_utils.py	View secret
-		Generic High Entropy Secret	ef77502	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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[saberuster]

@microsoft-github-policy-service agree

[sonichi]

@nerfZael could you take a look at this PR?

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 39.60%. Comparing base (4a44093) to head (68a514a).
Report is 39 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2426      +/-   ##
==========================================
+ Coverage   38.14%   39.60%   +1.46%     
==========================================
  Files          78       82       +4     
  Lines        7865     8355     +490     
  Branches     1683     1922     +239     
==========================================
+ Hits         3000     3309     +309     
- Misses       4615     4762     +147     
- Partials      250      284      +34     

Flag	Coverage Δ
unittests	39.54% <100.00%> (+1.41%)	⬆️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[AaronWard]

LGTM! 👍