MySQLdb relies on garbage collection to close the connection. Relying
on such asynchronous event as the garbage collector is never a good idea,
and this can cause issues when the transaction associated with the
connection is started: because the connector is being replaced, it will
never be properly aborted. So do not take chances and do not leak open
connections: always close it.

So that it's more apparent that we are not leaking a potentially active
transaction on that connection.

The same error code can be used for different causes. Specifically, it can
be used for SQL-level syntax error (which this code intended to handle),
or it can be used for fulltext syntax error (which makes this code raise).
Also, drop forced-reconnection, because this means a still-established
connection make be kept around and completely detected from current
transaction, which may cause a database snapshot to be kept indefinitely
(actually, until mariadb's timeout), in turn causing performance issue
because of associated InnoDB snapshot.

   title is undefined, use self.name instead.

/reviewed-on nexedi/erp5!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.