Do not trust users to give "official" DNS names at account creation time

Scenario:
A server has an official DNS name: really.dead.technical.long.hard-to-type.hard-to-remember.myfavorite-company.nuxeocloud.bzh
This server has a nickname (DNS alias): nuxeo.myfavorite-company.bzh
This server might have other alias as well

The user will instruct Drive client to connect to the nickname.
Thus, Drive will associate documents and tokens from this site with the nickname.

There are circumstances where the official DNS name might be retrieved (e.g. nuxeo.url has not been explicited to use the nickname, or is using another nickname, and the user uses Direct-Edit)
Thus, Drive receives a URL not matching any name it knows about.
Thus, Drive ends with a statement such as user USERNAME on server OFFICIAL_DNS_NAME... is not signed in Nuxeo Drive on this computer as it does not know which token to send back.

Requesting that the URL that Nuxeo will use is used internally as an equivalent key in Drive to the DNS nickname used to authenticate, e.g. for Direct Edit to work seamlessly