In a real ERP5 actions, roles etc are all indexed, so it's more
realistic to simulate update with full indexing.

This can help debugging test failures on test nodes

ERP5: Remove Capacity/GLPK: never used and broken since glpk Python module is not in ERP5 Software Release neither.

* Properly override WebSite Document in erp5_web_shadir by creating a new
  version_priority.
* Keep Web{Section,Site}TraversalHook in Product/ERP5/Document as these are
  not ERP5 objects. Also, add `kept_for_backward_compatibility_only` to
  importLocalDocument() to handle pattern where the Document class has been
  migrated but some code remains.
* Move WebSection_get*PrecacheManifestList Python Script from bt5 not depending
  on erp5_web to erp5_web_renderjs as this is required by CodingStyleTest
  (WebSection being now in erp5_web).

When a first migration was reverted for any reason (e.g. ConflictError),
the assertion failed because __setstate__ was not called yet to fix the
class back to the old one.

See merge request !1212

Fixes Active Process' "hasActivity" method when that document's uid is >2**32.

erp5_officejs_support_request_ui: Add begin date to the query when user click on "Last Month Activity"

The filter when the user click on the "Last Month Activity" chart filter Support Request only by status (Submitted / Open / Suspended / Closed). So on the table "Recent updates", all the support request with the chosen status appear. There is no filter by "Begin Date" for the last 30 days, which is no coherent with the "Last Month Activity". => It should appear only the support request with the chosen status with a begin date < D - 30 days

See merge request nexedi/erp5!1214

See merge request nexedi/erp5!1216

Base_viewDict does not produce valid html, showing the dict using showDict is enough

- use html5 doctype
- don't use i18n: tags where they are not processed
- use class instead of id for elements that are repeated
- remove Content-*-Type meta that are reported as invalid by nvu

this class does nothing and does not seem used

See merge request nexedi/erp5!1210

Make `erp5_configurator_standard` use `erp5_configurator_standard_categories`.

Since this is the business templates for standard (SME) configurator categories,
it seems logical to install this business template when installing SME configuration.

Before these changes, standard configurator was using a spreadsheet ( `standard_category.ods` ) to define the categories. Now this spreadsheet is almost empty, it only contain group and site that are custom and the configurated instance will install `erp5_configurator_standard_categories` business template.

The main goal was to make generated configuration use unit conversion module instead
of the obsolete quantity properties on quantity unit categories, but I thought it would make sense to use this `erp5_configurator_standard_categories` business template that is otherwise not used.

See merge request !1172