[Feat] asyncio for grpc data interactions

[jhamon]

Problem

Describe the purpose of this change. What problem is being solved and why?

Solution

Describe the approach you took. Link to any relevant bugs, issues, docs, or other resources.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Infrastructure change (CI configs, etc)
• Non-code change (docs, etc)
• None of the above: (explain here)

Test Plan

Describe specific steps for validating this change.

[gitguardian]

⚠️ GitGuardian has uncovered 6 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
14203991	Triggered	Generic High Entropy Secret	e665c0d	app2.py	View secret
14203991	Triggered	Generic High Entropy Secret	e665c0d	app3.py	View secret
14203991	Triggered	Generic High Entropy Secret	e665c0d	app2.py	View secret
14203991	Triggered	Generic High Entropy Secret	1c9632e	app2.py	View secret
14203991	Triggered	Generic High Entropy Secret	1c9632e	app2.py	View secret
14203991	Triggered	Generic High Entropy Secret	1c9632e	app3.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.}

[Noam-Barbiru]

We shouldn't panic if a namespace doesn't return results. It is ok to return zero results, like in a case where the filter filtered out all the vectors in the namespace.

[jhamon]

Thanks for calling this out. Jeff originally asked that we fail when namespace is incorrect, but that seems indistinguishable from the case where results are empty due to filtering. So I'm going to take this out.