Support urllib3 2.0.0

[sl0thentr0py]

Problem Statement

see if we need any changes and how the openssl support matrix works across runtimes (AWS lambdas etc)
https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html

[hartwork]

To add a bit more to the picture, lack of support for urllib3 >=2 already forces projects to either keep urllib3 in the past for Sentry or to keep Sentry in the past for urllib3, e.g. see Sentry bump pull request hartwork/jawanndenn#750 where merging is blocked due the dependency conflict.

[intgr]

Related PR that blocked urllib3 v2:

• Pin urllib3 to <2.0.0 for now #2069

[dimaqq]

> poetry show -t
...
requests 2.30.0 Python HTTP for Humans.
├── ...
└── urllib3 >=1.21.1,<3
...
responses 0.23.1 A utility library for mocking out the `requests` Python library.
├── pyyaml *
├── requests >=2.22.0,<3.0
│   ├── ...
│   └── urllib3 >=1.21.1,<3 
├── ...
└── urllib3 >=1.25.10
...
sentry-sdk 1.23.0 Python client for Sentry (https://sentry.io)
├── ...
└── urllib3 >=1.26.11,<2.0.0

Looks like Sentry is the last straddler... but I like Sentry!

Looking through #2051 that introduced the restriction, there's this comment:

The best fix here is actually to upgrade your runtime to Python 3.9+

Could the required version urllib3 be made conditional on the Python interpreter version?

The old AWS runtimes are not going away any time soon; GCP may be similar. So the problem won't disappear on its own.