Hatch doesn't respect build dependency versions

[dlqqq]

It appears that hatch doesn't respect specification of build dependency versions in the build-system.requires field as defined per PEP 518 when running post-install-commands. Instead it seems to inherit the dependency available in current Python environment.

To reproduce:

1. (optional) start a new conda environment and conda install pip
2. pip install jupyterlab==4.0.0a34
3. hatch new hatch-playground
4. Copy and paste the following gist into pyproject.toml. This specifies jupyterlab~=3.4 as a build dependency and adds it as an environment dependency as well. Then in post-install-commands, it prints the version of jupyterlab.
5. Verify the following output:

% hatch shell
4.0.0a34

The expected result is some version compatible with the specifier jupyterlab~=3.4, e.g. 3.6.1 instead.

I suspect that the same behavior happens during pre-installation and installation.

I've tried reading the docs and there is mention of "build targets" and "build hooks" dependencies, but it was not immediately obvious that it was relevant to my use-case. If there is a way to do this already in hatch, then this is a documentation issue and not a bug.