fix(native_image): fix C++ toolchain env setup

[fmeum]

Instead of relying on the default shell env, get the environment
variables declared by the C++ toolchain. On macOS, additionally use
apple_support to pass in DEVELOPER_DIR.

Since GraalVM sanitizes the environment, all variables are translated
into -E flags.

Fixes #67

[fmeum]

Stacked on #70 and #71

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[fmeum]

@keith This is what I came up with based on your diff. It works in Bazel CI :⁠-⁠)

[fmeum]

I can see how lambda and nested functions in general are problematic on Bazel 4. Unfortunately loading them conditionally isn't possible without either splitting out the non-legacy rules or using a Bazel version check in a repository rule and generating code.

We could also mimic what apple_support.run does and then directly control the way environment variables are passed to ctx.actions.run. Maybe @keith also knows a better solution.

[sgammon]

@fmeum see #80, i've performed the rule split and refactor in anticipation of that same problem. bazel4 is fixed, mac tests are working, and that PR now includes this one as well as #73

i hope we can move discussion to #80 where we can prep a release at 0.10.x 😄

as such closing this (but only as long as that PR works for your needs @fmeum -- if you hit issues we can always reopen this one.)