Add missing dependency

[ocelotl]

Description

Add wrapt for the gRPC instrumentation

Fixes #357

Type of change

Please delete options that are not relevant.

• 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

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A

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

[alertedsnake]

Why not ~= 1.0?
It should be noted that 2.0.0rc1 would fit the < 2.0.0 requirement.

[owais]

It should be noted that 2.0.0rc1 would fit the < 2.0.0 requirement.

That's a bit surprising to me but in any case, wouldn't that only be the case if --pre is used with pip install? Not advocating for one way to specify deps. Just curious about how it works exactly.

[alertedsnake]

PEP-444 says:

The exclusive ordered comparison <V MUST NOT allow a pre-release of the specified version unless the specified version is itself a pre-release. Allowing pre-releases that are earlier than, but not equal to a specific pre-release may be accomplished by using <V.rc1 or similar.

So you're right, but I'm now wondering why this has failed so much for me in the past? I've definitely released broken versions into production because an alpha version got dragged by a "less than the next major" requirement spec, and I've never used --pre. Strange.