Provision dev with upgraded pip

[isaacsolo]

Description

Recording some things @rickyrombo and I worked through provisioning a new box that had some issues running DP tests.

• Parity with using upgraded pip similar to the docker image:

  audius-protocol/discovery-provider/Dockerfile

  Line 40 in bdd6fa0

  python3 -m pip install --upgrade pip && \

  . Avoids weird issues where installs work in CI but not dev.
• Install packages for the correct version of python.

This change should help avoid others experiencing the same thing but we probably still want to use some package manager: pipenv, poetry, etc.

Tests

How will this change be monitored? Are there sufficient logs?

[joaquincasares]

Could you format the pip install to be within line 64's pip install in the same format as line 66, so pip==22.0.4.

This way, we lock our pip to a specific version (to help alleviate future transient issues when pip auto-upgrades silently).

Nice job on using pythonX -m pip which has never caused me issues!

[isaacsolo]

do we not want to automatically upgrade pip like we do for docker?

[joaquincasares]

Since we're having a bit of issues around A from different angles, I'd vote to restrict where these issues are coming from by locking down items that could change along our main path to running A up.

If we lock down pip to a specific version, that's one less thing we have to worry about shifting. The concern comes from issues like #2900 where the PalletsProject updated click and caused us to make a few changes to bump and lock down version.

Since pip is getting more powerful with dependency management (like what Ricky showed over our call), it'd be good to lock down the version as pip reworks their internal code.

If we're not locking pip to a version within our Docker image I'd vote to do that as well, even if through a different PR, but I think there's more flexibility there since the shipped Docker container will be the same for everybody. In this case, two different people can have different versions of pip depending on when they launched/provisioned their machine. This becomes more of a maintenance issue especially as the team is heavily rotating through boxes at the moment.

[rickyrombo]

Thank you!!