built-in "install" rule: verify well-formedness of resulting stage

The install target, like any other target, has to have artifacts
and runfiles being proper stages, i.e., in such a way that the
keys can be interpreted as names in the file system without causing
conflicts. This property used to be unchecked, thus allowing users
to define mal-formed targets that, when used as inputs to actions,
would result in unspecified layout of the action directory. Fix
this by adding an appropriate check enforcing well-formedness of
the resulting stage.

(cherry picked from f66db4bb21efeead140a453f91280bb9471f24a9)

0 files changed, 0 insertions, 0 deletions