Propagate custom env vars to the API checker soundness check:
This is needed as we use env vars to enable all traits in most CI pipelines for packages that have any non-default package traits.
Setting this env on the workflow that calls this one doesn't seem to do the job, maybe they need to be propagated explicitly? That's what we do elsewhere: https://github.com/apple/swift-nio/blob/888f4affd6cc7629adace9492c95504dd5201ae1/.github/workflows/benchmarks.yml#L168
cc @rnro