Set upper bound for requests instead of forcing new requests-toolbelt

[gordonhart]

Seeing issues installing latest on trunk as well as the latest 0.68.0 release on different environments. Looks like it boils down to the requests-toolbelt>=1 pin being too new (breaks compatibility with libraries that pin e.g. requests-toolbelt^0.9) and the requests==2.30 release causing issues in the ecosystem that haven't fully shaken out (see psf/requests#6443, psf/requests#6432).

This PR addresses the problem by unpinning requests-toolbelt, which should be driven mostly by the requests version, and adding an upper bound requests<2.30 with a TODO to rip out once things settle.

[ly-kolena]

Somehow cannot reproduce this using kolena-client-contrib/demo docker build as a testbed. Suppose better the old enemies we know.

[gordonhart]

One of the incompatibilities I'm seeing is with poetry installed in the same environment:

$ python3 -m pip install kolena-client
...
poetry 1.4.2 requires requests-toolbelt<0.11.0,>=0.9.1, but you have requests-toolbelt 1.0.0 which is incompatible.

I'm sure there are other common libraries that have major version pins on requests-toolbelt. I think it's best for us to give things time, rather than requiring a new major version a few days after it landed.

[codecov]

Codecov Report

Merging #11 (704409a) into trunk (6d4582c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            trunk      #11   +/-   ##
=======================================
  Coverage   85.52%   85.52%           
=======================================
  Files          93       93           
  Lines        5865     5865           
  Branches      640      640           
=======================================
  Hits         5016     5016           
  Misses        767      767           
  Partials       82       82