Add workaround for pip bug in dep resolution

[mikewilli]

Seeing an issue in CI or with a fresh venv when installing dependencies from requirements.txt. Seems to be related to an issue with pip, so we should add the workaround mentioned in the pip issue. See below for more info:

So I'm able to reproduce this locally with a new venv by just running python -m pip install -r requirements.txt, both on this branch and on main. I found a discussion and an open bug with pip, and the workaround mentioned there of using --no-deps with pip install fixes the problem for me. I don't see a downside to this for us because we are resolving dependencies with pip-tools generating the requirements.txt, so I think it's a valid workaround for us.

I'll put up a quick PR with this change shortly and then hopefully updating this branch with that change fixes the issue.

Still not sure why this suddenly popped up now. Perhaps some cached dependencies that expired or a particular dep update.

Originally posted by @mikewilli in #2047 (comment)

┆Issue is synchronized with this Jira Task