Run tests with lowest-direct resolution #13
Description
Currently, we don't have uv's dependency resolution configured, so although we declare lower bounds on (at least our production) dependencies, we're only testing with resolution=highest. Ideally, we'd add a matrix dimension where we tested with resolution=lowest so we know that our lower bounds are valid. From uv's docs:
When publishing libraries, it is recommended to separately run tests with --resolution lowest or --resolution lowest-direct in continuous integration to ensure compatibility with the declared lower bounds.
This will probably result in us adding a lower bound to httpx (and perhaps our development dependencies).
Here's an example PR where I did this in protovalidate-python.
If we want to do this, I think it makes sense to configure uv to use lowest-direct by default locally (again, protovalidate-python PR example), and then iterate on the dependency bounds until we get the checks working locally.