* Prepend portal type

* Migrate all documents instead of just the first one
* Modify dropbox configurator to use query setting if available

* Use coordinate_text instead of url_string in testOfficeJSBookmarkManager
* Add test for erp5 synchronization

* bookmark module -> url module
* url_string -> coordinate_text
* do not use text_content
* fix required fields

portal roles and live tests for curation_request, curation_record, decision and
web_bookmark

This action should only be possible if user have View History
permission.

erp5_data_protection relies on removing the "View History" permission to
make sure users cannot see the properties before protection in the
history tab. This was supported by Base_viewHistory, but not by ZODB
History

If we call Base_translateString before storing the message in the
history, the message will be translated when this action is used and
stored as translated using the language of the user executing this action.

The proper way is to store a message in history, so that it is rendered
when displayed.

Clone of nexedi/erp5!339

/reviewed-on nexedi/erp5!391

Also, document that value order in base_category_dict is meaningless.

@Nicolas uses worklist as one of many gadgets in one page thus stackable empty worklist is necessary (before it was positioned as an fixed element).

/reviewed-on nexedi/erp5!387

fixes #20170911-1AD62FB

Reports is easier to read if lines are sorted by third party name then
by date.

We also sort by transaction title to keep stable ordering of lines.

Use portal_membership.getAuthenticatedMember().getUserValue() instead.

This issue was reported by Nicolas. When embedding the
support request application in other App. The `options`
parameter in the `render` function is undefined, so the
`field_listbox_begin_from` can not be found. Use
`getUrlParameter` to retrieve it from URL.

The commit 1fbf9ba9 put
the title in wrong order. Correct it. This commit is not
a revert, it is a fixing.