Better handling of duplicate (versioned) dependencies

Currently, if i) a project specifies a versioned dependency on another project, ii) a submodule specifies an un-versioned dependency, and iii) The latest version is newer than the versioned dependency, then that second project will appear twice in the dependency calculation.

We should be able to detect this scenario and force the unversioned dependency to match the versioned one.