/reviewed-on !996

Folder_getDeleteObjectList could do an extra paranaoïa check that the
caller did not pass an empty list of uids, because this would cause the
script to iterate on the full catalog table.

We now have getRelationCountForDeletion API for this.

The general approach is:
- replace deprecated lambdas with list comprehensions
- remove unused variables/imports
- replace dangerous arguments [] with ()
- replace dangerous arguments {} with None and "if None -> {}"
- replace builtin names with something similar

Now that all problems reported by pylint are fixed, enable coding style
test.

This was not valid HTML5:

  AssertionError: Using nu validator to parse the view "SQLMethod_view" (from erp5_core bt) with warnings displayed :
  Error: line 782 column 23 : Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.): </script>
  <style type="text/css">
    .cm
  Error: line 822 column 23 : Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.): script>

  <style type="text/css">
    .max

This fix a regression from 920655a2 : when item has no tracking, uid was
passed an empty list and this fetched all catalog.
Also call getObject explicitly only once instead of having it called
implicitly twice.

/reviewed-on !988

/reviewed-on !1000

/reviewed-on !1002

- indent the json representation of error
- if error is an XMLHttpRequest:
  - include the server side error response in an iframe
  - split response headers

/reviewed-on !981

/reviewed-on !1004

erp5_project does not depend on erp5_budget, so instanciating project
cell fail unless erp5_budget is installed.

Project Cell are not used by default, so it's still a bit unclear, but
with erp5_budget we can directly define budgets by project / project
lines in a more flexible (but also more complex).

Project Line uses OrderLine, so it's consistent to use OrderCell for Project Cell.


/reviewed-on !980

erp5_trade_ja: 軽減税率8% tax line in summary must always be present (official specification) but is not used in Nexedi so hardcode it.

erp5_trade_ja: AttributeError was raised when default_image (to display logo at the top left) was not defined.

- views/actions meant for officejs should use "object_jio_x" categories to avoid conflicts with erp5js
- using object_jio_search instead of common object_jio_view because the base form for rendering depends on the category (form_list, form_dialog, form_view, etc)
- changes are also in bts officejs_jquery_app and officejs_ooffice

- do the calculations while officejs router set settings

speedup

 - run `testXHTML` on business templates "one by one"
 - fix all the problems with the currently tested business templates
 - because `erp5_ingestion` was containing some tests skin folder depending on other business templates and because I did not want to add dependencies to `erp5_ingestion` I moved the tests in `erp5_ingestion_test`.

/reviewed-on nexedi/erp5!989

Some document subobjects have a workflow, and so, can be only be deleted from some state
If the listbox does not display them, do not add the state filter parameter

This skeleton became cloudooo several years ago and we don't need this
here anymore.

/reviewed-on nexedi/erp5!966

Note that Set type setter still keeps the default one if exists.

/reviewed-on nexedi/erp5!862

This property sheet was missing, but test passed because both the
setSourceReference and getSourceReference were acquired

/reviewed-on nexedi/erp5!998

/reviewed-on nexedi/erp5!999

This will allow to find problems when only business templates and their
dependencies are installed. When we run testXHTML with all business
template installed we don't see problems that may happen only when some
business templates are not installed.

pylint complained about indentation

this was removed in 2138aee5

This bt has too many coding style problems for now