Relax dependency pinning

[stevenbunting]

Still figuring out the best practices for dependencies in a client library. I'm used to pinning dependencies in an app to the minimum viable set, but in a library you want to be more careful about allowing for more permissibility.

At some point it'd be nice to do a full audit, but realistically we'll probably just expand permissions when the need arises like we're currently doing. I'll develop some test scripts to make expansions like this less manual.

Addresses Issue #41

Locally all tests pass with dependencies upgraded to the minimum and maximum allowed values. Checking to see if they pass on GH. Will test with the api testbed before I request review

[stevenbunting]

picking this back up. Ran test suite on new dependencies. Don't see any significant deviations. Anecdotally uses slightly less memory but not sure if attributable to dependencies.