Rule collision when multiple vendored projects contain executables with matching names

Expected Behavior

It should be possible to vendor multiple packages which contain executables whose names (public_name in dune files) are the same. The source code for a package may contain executables for testing and experimentation, but typically one vendors a package just to get access to the libraries it contains.

Actual Behavior

When resolving install stanzas that target the bin section, or expanding %{bin:...} expressions, dune gives an error Multiple rules generated ...

Reproduction

I've made a small project to reproduce the issue: https://github.com/gridbugs/dune-vendored-projects-rule-collision-repro

It vendors two packages: OSCADml.0.1.1 and scad_ml.1.1.0. Both those packages contain executables named "circle". The dune file contains an install stanza which installs a shell script into the bin section. Running dune build @install gives the error:

Error: Multiple rules generated for _build/install/default/bin/circle:
- vendored/scad_ml.1.1.0/test/dune:3
- vendored/OSCADml.0.1.1/test/dune:3
-> required by
   _build/default/dune-vendored-projects-rule-collision-repro.install
-> required by alias install

Specifications

• Version of dune (output of dune --version): 3.6.1
• Version of ocaml (output of ocamlc --version): 5.0.0
• Operating system (distribution and version): NixOS (linux 6.1.1)

Start with the linked reproduction project and run dune build @install to reproduce the collision. Inspect the install stanza and the conflicting vendored/scad_ml.1.1.0/test/dune:3 and vendored/OSCADml.0.1.1/test/dune:3 entries. Done means multiple vendored packages with matching executable names no longer produce duplicate rules when resolving the bin install section or %{bin:...} expressions.