When an error was encountered in `jIOWebSection`, it did not abort the
transaction, as it usually does in ERP5. This was made on purpose because
errors are logged in ZODB, hence aborting the transaction didn't make it
possible.

This behavior was annoying, so this commit purposedly abort transaction before
starting a new one to handle error. We are therefore able to log error in ZODB
while also keeping the usual ERP5 behavior of aborting on error.

Unindex, create and drop are managed by catalog

As it is the string, make it of fixed string

As get and put actions are deterministic there is no need to loop
over various schemas when checking data. If there is an error it is
returned directly.

* allDocs now behave like others action mode and return the result
of the match
* It allows greater customization of the output data

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