* chore: avoid checking instance on each stream call* fixed indentation* added check for unary call* fixed type check* fixed tests* fixed coverage* added exception to test class* added comment to test* 🦉 Updates from OwlBot post-processorSeehttps://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md---------Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

* feat: optimize _GapicCallable* cleaned up metadata lines* chore: avoid type checks in error wrapper* Revert "chore: avoid type checks in error wrapper"This reverts commitc97a636.* add default wrapped function* fixed decorator order* fixed spacing* fixed comment typo* fixed spacing* fixed spacing* removed unneeded helpers* use caching* improved metadata parsing* improved docstring* fixed logic* added benchmark test* update threshold* run benchmark in loop for testing* use verbose logs* Revert testing* used smaller value* changed threshold* removed link in comment

* fix: fallback to unary_unary when wrapping async callablesWe recently [made a change](ab22afd) to move some computation in the async rpc wrapper from call-time to wrap-time. This way, individual calls would execute faster, since they don't have to re-compute some data on each callA side-effect of this change is that now some [type validation](https://github.com/googleapis/python-api-core/blob/d96eb5cdd8120bfec97d62b09512c6fecc325be8/google/api_core/grpc_helpers_async.py#L209) happens earlier. This caused some downstream tests to fail when a mock grpc channel is used. The wrapper doesn't know how to handle the mock.Mock type, and raises an exception while constructing the client objectThis PR fixes the issue by falling back to the unary wrapper when the callable type is unknown, rather than raising an exception. This is in-line with how [the sync version handles it](https://github.com/googleapis/python-api-core/blob/d96eb5cdd8120bfec97d62b09512c6fecc325be8/google/api_core/grpc_helpers.py#L198)* fixed elif to if* removed outdated test

* Ignore unknown fields in rest streaming.If the api adds a new field to a stremaing response, it shouldn't break old clients.We found this in the google.ai.generativelanguage API. Colab forces our clients to use rest, so all our streaming examples broke when the API team rolled out a new field.* format---------Co-authored-by: Anthonios Partheniou <partheniou@google.com>

* chore: move retry async check to wrap time* 🦉 Updates from OwlBot post-processorSeehttps://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md* added no cover mark---------Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>Co-authored-by: Anthonios Partheniou <partheniou@google.com>

This reverts commitd96eb5c.

…)" (#667)This reverts commitac098a7.

* fix: add support for protobuf 5.x* remove pin for types-protobuf* remove pytest from noxfile* refactor common code* RefactorCo-authored-by: Victor Chudnovsky <vchudnov@google.com>* run black* 🦉 Updates from OwlBot post-processorSeehttps://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md* mypy* run pre-release test against all python versions* filter warning---------Co-authored-by: Victor Chudnovsky <vchudnov@google.com>Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>