Assuming that the test database already exists and 'movement' table already
contains data (from past execution for example), on '--save' before this
commit:
  1. Create a new ERP5 Site:
     1. Install erp5_mysql_innodb_catalog.
     2. Call ERP5Site_reindexAll(clear_catalog=True) (from ERP5Generator.setupIndex()).
        => At this point, erp5_mysql_innodb_catalog tables are recreated.
  2. Install erp5_movement_table_catalog or any bt5 adding a new SQL table.
     => This does not recreate the table and leave the existing data as it is.
  3. Dump MySQL database to dump.sql.
  => dump.sql contains 'INSERT INTO' for 'movement' table *before* this '--save'.

This fixes random customer Unit Tests failures on SQL queries accessing
'movement' table directly and getting {non-existing,past executions}
Movements.

With this commit, after installing all bt5, all tables handled by the Catalog
will be cleared and ERP5Site_reindexAll will be called.

/reviewed-on !918

[erp5_ui_test_core, erp5_dms_ui_test, erp5_km_ui_test, erp5_configurator_standard_ui_test] setFile command does not need pause command now.

[erp5_web_renderjs_ui] Show select column in view dialog if listbox's select column checkbox is checked.

[erp5_configurator_standard_ui_test] Fix file uploading tests. Use setFile selenium command to avoid security error.

31804f68 was merged too soon.

/reviewed-on nexedi/erp5!913

It was possible that the previous server socket did not have enough time
to expire, which could cause an "Address already in use" exception.

url
- corresponding test added

- improve OfficeJS applications by reducing the quantity of code to be written and reuse the ERP5 configuration (portal_type, actions, forms, etc.) instead to generate the app

  The API changed on the slap, this commit follow up the changes.

Which is useful when debugging tests

Some files in the Skin Folder was not deleted by mistake

/reviewed-on nexedi/erp5!914

'only_visible' in essence checks 'Add portal content',
But here we care for View permission really, since user can have worklist in a document
even if he/she does not have the rights to add content to the module.

otherwise naturalWidth/naturalHeight may be 0