Lookup cross compile config paths with runtime OUT_DIR vs compile time

[abrisco]

This change addresses a build failure I found when building Bazel rules for PyO3 (abrisco/rules_pyo3#14). Essentially, because Bazel compiles and runs build scripts in a sandbox at different locations, when environment variables that refer to a directory are compiled into build scripts, the directory embedded is to an old sandbox location that will not exist for any other action (running build scripts, compiling). This change resolves the build failure by using the OUT_DIR environment variable at runtime vs compile time to locate a cross compilation config.

This change would have the side effect of these config files not being written into pyo3-build-config's OUT_DIR but the OUT_DIR of whatever the crate was linked into. This is because when the pyo3-build-config's rlib is compiled, it's OUT_DIR will be embedded into it then, thus providing a locked absolute path for it's consumers.

[davidhewitt]

Thanks very much for the PR! I think you're right that there's a problem here, but I worry that this isn't the complete solution. I'll write up my observations in an issue now...

[davidhewitt]

See #4579

[davidhewitt]

Given that there's a more complex problem here, which I don't think this solves, I will close this PR. Let's please continue figuring out what to do on #4579.