Packages with the same names leads to undefined behavior

| Title | Description
| --------------------|------------
| Version | 0.24.5
| Type | feature Request
| node | 12.16.3
| Operating System | OSX
| Short Description | in short - there is a foot gun
| Detailed description| ....

When new packages are created via copy-paste it is possible to forget to rename a package, having as a result a few ones named in the same way.
This lead to some issue at the linking stage, when _some_ packages would not be linked together. In my case, having 3 similar packages, I have a problem with only one package not linked into the middle of my duplicates.

I know that the root cause sounds a bit stupid. It is. But it's really easy to run into it, and I've spent 4 hours 😅 not able to `start` my project (and discover the real problem) or `commit` it due to linting issues (using of unresolved dependency).

### Expected solution:
Bolt should throw an error if two packages of a same name were found.

Start by tracing Bolt's package discovery and linking flow, then look for existing tests around workspace package names. Done means duplicate package names are detected and reported as an error instead of allowing incomplete linking.

Written by the indexing model from the issue text.