Pipfile.lock specific to the python version

[mtrofin]

Some packages, e.g. dm-reverb, have different hashes between 3.10 and 3.11. This patch separates Pipfile.lock into per-version files, and adds a wrapper, versioned_pipenv, that uses the version-specific lock file. It does so by copying the version-specific Pipfile.lock in the repo root. Note that we gitingore that name, as it becomes a temporary artifact of running versioned_pipenv.

We could have made the copy elsewhere, but that makes certain variants of pipenv subcommands (like run) not work.

[boomanaiden154]

What is the purpose of updating the lockfile now?

It also looks like the Dockerfile should be in a separate PR?

[mtrofin]

What is the purpose of updating the lockfile now?
the pipenv sync in the (now removed from this PR) demo Dockerfile isn't happy about some dependencies.

It also looks like the Dockerfile should be in a separate PR?
yes, fumbled

[boomanaiden154]

I'm not a big fan of a python wrapper around pipenv, and would probably prefer we just add directions to manually copy the pipfile, but I guess this works for now.

[mtrofin]

I'm not a big fan of a python wrapper around pipenv, and would probably prefer we just add directions to manually copy the pipfile, but I guess this works for now.

Or maybe we switch to another similar mechanism that supports this scenario (if it exists)?