RM-108 remove upper bound on google-api-python-cli

[ryantimjohn]

No description provided.

[Brunope]

maybe a <2 is in order here for future proofing?

[Brunope]

what is the context behind this change?

[ryantimjohn]

@Brunope, to @naswierczek 's point, it's now becoming accepted wisdom in Python package distribution to remove all upper bounds on required packages, then have a system like we do with daily builds + making future warnings trigger failures to catch errors early, then build compatibility with newest package versions wherever possible. Break early and fix. This gives your package the least likelihood of having dependency incompatibilities with other packages that people need in their workflows. Only where there's a genuine inability to make your package incompatible with most recent versions should you have upper bounds.

I'm going through all of our upper bounds now one-by-one and seeing if we can reasonably remove them.

Here's an article about this:
https://iscinumpy.dev/post/bound-version-constraints/

[ryantimjohn]

@naswierczek why'd you remove you supportive comment =p

[naswierczek]

@ryantimjohn I certainly didn't do it on purpose! I don't know why the comment got removed!

I still support removing bounds unless we know something will break. If we have to stay on an old version for reasons, we should keep any upper bounds we have. Otherwise if an upper bound can be removed it should be. :)