[Feature request] UI features to avoid duplicates

Unwanted duplicates are really a pain, so first thing should be to help avoid them :

1- When copy/pasting a object "Client", the second should be named "Client #2" rather than "Client (copy)", preserving the unicity of names. As several objects "Client" are existing, copy/pasting an object "Client" could result in a new "Client #16", "Client #17" and so on.

2- When creating a new object (drag dropping from palette),
while we name it, there should be a intellisense-like list showing the existing objects with approx the same name. User should be allowed to select it from the list, so it will refer to an existing one, and avoid creating a duplicate.

3- When renaming an object, intellisense-like list should be able to replace the new object with a reference to the existing object, even few days later.
Scenario 3a : I placed a bunch of "business actors" items in my view. Some days later, I start to name them correctly, one of them I want to rename from "Business Actor" to "Client", however, as "Client" actor already exists, I can select it, and Archimate Tool prompt me : "Do you want to fusion this object into existing object 'Client' ?"
- If I say yes, I end up with only 1 object "Client" that contains what I did put yesterday and what was in older Client object
- If I say no, I end up with 2 distinct objects
a) "Client" (the old one)
b) "Client #2" (my new one) with 2 different contents.

4- if some people dont want to see the "#nn" behind the names,
option a) - interface could have an option to hide them, or make them appear in smaller or lighter font
option b) - user could just manually change back a "Client #2" to "Client" and keep two different objects with the exact same name (bad in my opinion)

The issue names no files, tests, or entry points. Review the four duplicate-handling scenarios in the Java desktop UI and determine which behaviors belong in one scoped change; done should be defined by an agreed design covering copy/paste naming, name suggestions, merging or retaining objects, and display of numeric suffixes.

Written by the indexing model from the issue text.