Make GRPC a drop in replacement

[mcpaddy]

Problem

To make the GRPC version a drop-in for the normal client. For example LangChain.

Solution

Alias the function get to result.

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

Test using LangChain and my own code. There should be no need for this with the change.

    if mode  == 'GRPC':
      [async_result.result() for async_result in async_results]
    else:
      [async_result.get() for async_result in async_results]

[gitguardian]

⚠️ GitGuardian has uncovered 2 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
10042887	Triggered	RSA Private Key	96d6994	tests/integration/proxy_config/.mitm/proxy1/mitmproxy-ca.pem	View secret
10042888	Triggered	RSA Private Key	96d6994	tests/integration/proxy_config/.mitm/proxy2/mitmproxy-ca.pem	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.}

[jhamon]

I'm addressing this in another PR in a way that will include tests, etc.