Add Couchbase Vector DB Example Notebook and Minor Bug Fix

[lokesh-couchbase]

Why are these changes needed?

Added notebook example for Couchbase vector db.

Fixed minor bugs which leaked passwords to console and added id inside the document.

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	e42837d	test/oai/test_utils.py	View secret
10404693	Triggered	Generic High Entropy Secret	e42837d	test/oai/test_utils.py	View secret
12853599	Triggered	Generic High Entropy Secret	e42837d	test/oai/test_utils.py	View secret
10404694	Triggered	Generic High Entropy Secret	e42837d	test/oai/test_utils.py	View secret
12853601	Triggered	Generic High Entropy Secret	e42837d	test/oai/test_utils.py	View secret
10404696	Triggered	Generic High Entropy Secret	e42837d	test/oai/test_utils.py	View secret
10422482	Triggered	Generic High Entropy Secret	e42837d	test/oai/test_utils.py	View secret
12853602	Triggered	Generic High Entropy Secret	e42837d	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.}

[rysweet]

this gitgaurdian failure looks like a false positive to me - not sure how to resolve.