added conditional calling of unary_unary etc functions in _InterceptorChannel

[VamsiKrishna1211]

Fixes #2483

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Installing the grpc contrib package along with grpc>=1.63.0 version.

Does This PR Require a Core Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: VamsiKrishna1211 / name: Vamsi Kocherla (eef229e, 9200bff, a0ad24c, 0f999de, f4faa83, 7afc68a, 98f34b0, fb9bcc1, cb250e8, 629c5fc, 2c2c25d, b310b4c)
• ✅ login: lzchen / name: Leighton Chen (023edcd)
• ✅ login: xrmx / name: Riccardo Magliocchetti (03c6392)

[xrmx]

@VamsiKrishna1211 care to add a test with updated test requirements so we can actually test it in CI?

[VamsiKrishna1211]

@xrmx Yes sure.
This is my first contribution to otel-contrib repository.
So please let me know if I have to make any other changes in the PR. :)

[xrmx]

@xrmx Yes sure. This is my first contribution to otel-contrib repository. So please let me know if I have to make any other changes in the PR. :)

Cool! tests and an entry in CHANGELOG should be enough

[VamsiKrishna1211]

Cool! tests and an entry in CHANGELOG should be enough

@xrmx The changes in the PR pertain to instrumentation-grpc only, and I need to test with multiple versions of grpcio package. More specifically grpcio>=1.63.0 and grpcio<1.63.0. Because there is a breaking change introduced in the methods of Channel class in latest release of grpcio==1.63.0.

Is there any standard way already you guys follow to test these kind of scenarios?

[xrmx]

@VamsiKrishna1211 you can take a look at opentelemetry-instrumentation-httpx both in tox.ini (grep for httpx) and in the instrumentation package dir

[VamsiKrishna1211]

@xrmx Thanks for correcting the _registered_method argument, I think missed it by accident.

[xrmx]

@VamsiKrishna1211 could you please add a CHANGELOG entry? And fix lint and CLA please

[VamsiKrishna1211]

@VamsiKrishna1211 could you please add a CHANGELOG entry? And fix lint and CLA please

@xrmx Apologies for the delayed changes, was caught up with my full-time work for a while.
Added the changes to CHANGELOG and fixed the CLA, please check and let me know for any other issues.

[VamsiKrishna1211]

@xrmx Updated the repo with the changes.

[VamsiKrishna1211]

@aabmass Can you look into the MR? We're currently trying to update our packages to their latest version (Official nvidia-triton-client package mainly) while also using open-telemetry. But is causing issues because of the issue attached to this MR.