The fixes from !630
were not enough, exceptions set on days were calendar did not repeat
were also confusing other exceptions after this.

Simplify implementation a lot, instead of keeping track of the next
exception date, start by building a set of all exceptions dates and
use membership of this set as a criterion to skip exceptions.

backport of https //lab.nexedi.com/nexedi/erp5/merge_requests/1030

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

Use monaco editor with https://github.com/joe-re/sql-language-server
completion provider bundled in
https://lab.nexedi.com/jerome/monaco-editor-sql-completion-provider
This completion provider is not perfect, but codemirror's one was not so
good eiher. At least we can use monaco editor.

Also add a quick "copy to cliboard" feature, which copies the table as
html or in markdown format for text.

And also fix Server-Timing header that was an obsolete syntax no longer
supported by chrome.

component: We don't need Permissions.ModifyPortalContent to check consistency. Permissions.AccessContentsInformation is enough

This script was returning organisations in random order !

When organisation does not have accounting periods, but another organisation at the same level of the same group has, the result was undefined.

This fixes by considering all organisation from the same group.

This is enabled for title and description only, because that's usually
what we put on "external" documents such as invoices.

By "resource" here it means products, services, components and their
individual variations

instead of implementing this logic in ZSQL's DTML

cf 2c54e0f5

With this, we accept users with permission to Modify portal content or Associate role

With this, change we accept users with permission to Modify portal content or Associate role

jerome/erp5!6 rebased and in a big
commit so that we can start using that
SimulationTool: implement "linear" flow API

testInventoryAPI: silent pyflakes warnings

more interpolation implementation

inventory_list interpolation flow: support at_date & to_date

more and more interpolation API

interpolation

interpolation

group_by_time_sequence_list

testInventoryAPI: move inventory valuation methods in a dedicated test class

This should not be in test inventory list.

test: move Tracking API to a dedicated test module

inventory api: dirty way of disabling cache if keys such as node_category are used.

interpolation: security on SimulationTool_zGetInterpolationMethod

SimulationTool_zGetInterpolationMethod is called in restricted context
of Resource_zGetMovementHistoryList so it needs to be usable by
anonymous.

ZSQL Method does not read parameters from REQUEST, so it looks safe.

We should be able to configure a group calendar saying that the pattern
is "from 9:00 to 12:00, repeat every monday morning" with a group
calendar assignment saying "use this pattern from 01/01/2016 until
31/12/2016" and then create another group calendar assignment for 2017
without having to change the periodicity stop date on all presence
periods of the group calendar.

I think it should repeat from group calendar assignment's start date
until min(group calendar assignment's stop date, presence period's
periodicity stop date).

(cherry picked from commit b42a9c11)

because Domain.getRelativeUrl (and Category.getRelativeUrl) cannot be
restrictedTraverse'd

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 !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.