Allow working on models based on repositories having the same name

[jbsarrodie]

When importing a remote model to the workspace while the target folder already exists, we get this kind of "Folder is not empty" error:

I think we should manage this in a more user friendly way.

I can see two strategies:

1. Keep current behavior but use the FQDN or the repo instead of only the repo name. This would lead to more unique folder name and would solve the root cause.
2. Change the behavior so that when this error is raised, we ask the user if he/she wants to cancel or continue. If he/she wants to continue, then we add some randow text at the end of the folder name to be created.

The first option seems easier to manage, but the second has the advantage to allow someone to import a model more than once. Of course this should not be done unless you have a very specific need (TBH, the only use-case I see is us trying to simulate several people working on the same model, but for this I usually manually change the folder name anyway).

[jbsarrodie]

Closing as this duplicates #104