Potential issue with Bazel pywrap_library rule

[danilaml]

Discovered in tensorflow/tensorflow#100606 .

Looks like pywrap_library is run both before and after selects are evaluated in Bazel, so this https://github.com/openxla/xla/blob/main/third_party/py/rules_pywrap/pywrap.impl.bzl#L373
check could succeed for None values wrapped in select which seems unintended.

[danilaml]

Would be nice to get some update on this issue since while it blocks my patch in tf (tensorflow/tensorflow#100606) it may also lead to silent misconfigs in existing code (due to any select in common_lib_version_scripts being used in "unresolved" state at analysis stage).