When specifying remotes as URL parameter, implicit remote names should be the user/organization name

[dkwon17]

Is your enhancement related to a problem? Please describe

This enhancement comes from a discussion here: eclipse-che/che-docs#2531 (comment)

When remotes are provided to the factory url in this format:

{CHE_HOST}/#{GIT_URL}?remotes={https://github.com/dkwon17/che,https://github.com/eclipse/che,https://github.com/user1/che,https://github.com/user2/che}

The implicit names for the remotes are as follows:

origin -> https://github.com/dkwon17/che
upstream -> https://github.com/eclipse/che
fork1 -> https://github.com/user1/che
fork2 -> https://github.com/user2/che

Describe the solution you'd like

Instead of having the last two implicit names be fork1 and fork2 it would be great if their names were the user or organization name instead.

In this case, they would be:

user1 -> https://github.com/user1/che
user2 -> https://github.com/user2/che

Alternatively, having all of the implicit names be organization names could be useful too:

dkwon17 -> https://github.com/dkwon17/che
eclipse -> https://github.com/eclipse/che
user1 -> https://github.com/user1/che
user2 -> https://github.com/user2/che

Describe alternatives you've considered

Additional context

No response

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.