pip_parse: lockfile for build dependencies in repository rule

Since [PEP 518](https://peps.python.org/pep-0518/) projects can specify their build system requirements in their pyproject.toml file. Currently this is not included in the pip-compile and therefore can lead to non-reproducible issues. This happened in the wild today because pyyaml depends on cython but didn't pin its major version, so when cython pushed an incompatible version this broke if you were including it in bazel. One of the potential workarounds is to install the compatible cython version in the venv _before_ installing your requirements, which I also don't believe is possible. I believe supporting this would require pip-tools to also support this option, which is potentially implemented by https://github.com/jazzband/pip-tools/pull/1681

Start by reviewing the pip_parse repository rule's current pip-compile flow and the referenced pip-tools pull request #1681. Determine how build-system requirements from pyproject.toml should be included, and consider the work complete when those dependencies are locked reproducibly for repository builds.

Written by the indexing model from the issue text.