- configurations like form definitions are saved as objects into data-storage.metadata to allow jio.get

- this prevents the appcache-local storage sync to store unnecessary resources like gadgets

- hardcoded JSON was removed
- form definition is get from jio storage (erp5 for now)
- rendering is done in controller.js using form definition and context (jio document)

Notify the user and redirect to the storage page to force user to enter credentials if needed

 * Review SMS sending API to move the complexity and the various parameters from the interface script `ShortMessage_send` to the gateway interfaces.
 * Fix problem with mobyt with messages longer than 140 characters
 * Fix [#20170709-17309B6](https://nexedi.erp5.net/bug_module/20170709-17309B6)
 * add an (incomplete) test


/reviewed-on nexedi/erp5!580

![image](/uploads/f86e89066db17979735f892c5c36a90f/image.png)


This introduces a new portal type group "payment request"

/reviewed-on nexedi/erp5!831

This fixes the issue that a transaction with many big messages failed to
commit. By dynamically find the maximum allowed size of a query, it also
speeds up insertion by minimizing the number of queries.