Hey folks, could we: • in the context of PEX entrypoint resolution • if an entrypoint is provided • the target of that entrypoint is ambiguous • and we cannot resolve that ambiguity raise an error (or follow the unowned_dependency_behaviour)? context https://pantsbuild.slack.com/archives/C046T6T9U/p1704305637398089 , where a newly created ambiguity and the default of just returning the empty list cause an empty PEX to be produced.