Persist the server's UI into the local configuration database

How to reproduce

• Install only webui and drive on a server instance
• create a new workspace and add some files to it
• sync the files with drive
• try to edit one of the files metadata from your computer drive folder
• you go to a not found page(error)

Issue

Drive is using jsf by default and if the server configuration has not been retreived before the Direct Edit call, then the UI will be wrong.

Solution

When retreiving the Drive configuration from the server, store it into the local configuration database in the form:

• name: ui
• value: either jsf or web

Then, when generating URLs, instead of using Options.ui, take the value from the configuration.
Last thing, Options.ui will become obsolete, we should remove it.