* use get Input Schema of JSON form
* get schema url uses absolute url.

* Introduce Separate JSON Schema Form Editor Gadget
* Introduce Separate JSON Schema Text Editor Gadget
* Add djv for simple validation in Text Editor Gadget
* Introduce Switch Editor Gadget to easily switch from form to text
* Always displays response
* Lint code
* Remove manual html manipulation and use domsugar
* Display API related information at the top

* this is inconsistent with Base_checkAlarmConsistency

erp5_api_style: Add Page to display all API Actions

erp5_api_style: fix http method on json page and add cancel url

erp5_api_style: Fix reenable button after form submit with invalid data

erp5_api_style: Fix Get and provide default get Schema

erp5_api_style: JSON Form gadget now render response

erp5_json_form: jsonschema-form-gadget handle "Const", add checkValidity and liveValidate

erp5_json_form: react from add readonly and fix render when input json change

erp5_json_form: React form Hide danger panel to prefer display error inline

erp5_json_form: react jsonschema form gadget use typeof to be compatible with firefox 68

* Case of required properties

  Allow the developer associate a Mixin on Business template level
without require to overwrite the portal type itself

  Include mixins can be done in the same way, allowed content types or
property sheets are set.

erp5_administration: Add Scripts for Alarm to update validation state according to consistency state

    If two open orders are validated on the same transaction, archivePrevious script will get the an already archived as catalog will be outdated.

  Please squash me in future.

  If the user wants actitivites, it should create multiples StandardBT5ConfiguratorItems,
  This should accellerate Tests based on ERP5Configurator.

  This should be recoded, but it should speed up bootstrap of a site,
  as get modified objects are not called.

It the user don't have fully permission on the object (already changed state), this set will fail to check if source should be defined.

  The upgrade ordering seems buggy and requires to force reinstall it

This allow during a subscription process, create a user and them create all
documents using that user w/o rely on proxy roles (keeping good ownership
across the documents).