We should use schema_url rather them json_url on validationJSON, since the json_url is the software.cfg.json while schema_url is the actual url for the schema.

See merge request nexedi/slapos.core!380

   Use proper trademarks for the login buttons

See merge request nexedi/slapos.core!379

    This prevent not configured sites show the sign-in buttons w/o proper configuration, in other words, broken buttons.

  Just let configuratior handle everything

   Since the ID is used, it is important to "enableGlobal" before set conversion server configuration.

   Roles had duplicated names and were generating unecessary diff

See merge request nexedi/slapos.core!378

* jslint
* drop duplicated loopEventListener
* use rjs.onEvent method to reduce the number of created listeners
* use domsugar to make the code more readable
* start to use mutex

See merge request !377

  Include general tests for the revoke/generation

See merge request !375

This commit remove the following 2 commands:
 * slapos cache lookup
 * slapos cache source
And introduces the following 3 commands:
 * slapos cachelookup binary-sr
 * slapos cachelookup url
 * slapos cachelookup pypi

This is useful to check if some objects are in shacache for buildout.
Please note that the commands are using the latest keys (introduced in
slapos.buildout!26)

See merge request !376

   On xml serialisation we support a more restrict scope them the whole json schemas and on json-in-xml, despite the fact we could support all, not everything is suitable for form generation.

   The both "meta schemas" are a variation of the draft exclusively for UI rendering purpose.

   Keep this code would only make things confusing, since this code is mostly an archive

   If they exist.

Since the way of renaming the software_release_url proven to avoid having
unexpected results AND it is required in many cases to directly destroy an
instance, allow direct destruction of such instances.

See merge request !374

   This allow user edit the text area to fix the parameters and try to reload the form.

   This feature isn't used or required anymore.

   Whenever a user changes the Raw XML them return to the form, the  changes on XML are loaded into the form. This allow the user reuse a known xml form as template.