Introduce temp_object parameter on builder.build() and propagate it
 over until the newContent() calls. This change allow use create
 Temporary Documents intestead real ones, like a "preview".

(cherry picked from commit 959776ce50c2e7ee2b8f9945ec91a2e0fbe08619)

Conflicts:
	product/ERP5/Document/SimulatedDeliveryBuilder.py

- Dates Are now using ISOString providing efficient sorting as string
- modification_date property is not saved on object
- Modified conflict_handling parameter to overwrite the remote document with local content (no loss of data)
- the three different storage use different local databases

This caching policy should be the default for any offline webapp, to prevent any mistake done with the html5 cache manifest.

This reapplies commit 648d7020

Also enable pretty printing of kw and activity_kw

* Use editable fields with `pre` style for listbox columns
* Display h:m along with start date

Also fix a naming issue with one field

When searching accounts by validation state, the stat of number of movements on an account could be wrong

ERP5Site.log and Base.log are wrappers to the 'log' function from
Product.ERP5Type.Log, but parameters were forwarded in a wrong way
when called with a single argument:

  self.log(message) # Base method

This was equivalent to:

  log(message, '')  # function from Product.ERP5Type.Log

And the whole message was later part of subsystem in:

  logger = logging.getLogger(subsystem)

But because loggers are never freed, it is important that 'subsystem' does not
vary too often, to avoid a memory leak.

The fix is to simply forwarding parameters with catchall arguments, instead of
duplicating the signature from Product.ERP5Type.Log.

Of course, it remains important to call these methods correctly, otherwise
memory leaks can happen again. For this reason, catchall arguments also
prevents ERP5Site.log and Base.log to be called by ZPublisher.
Reported-by: Kirill Smelkov <kirr@nexedi.com>
Reviewed-by: Kirill Smelkov <kirr@nexedi.com>

Now you can sort results by full text search score, for example.

Now we have explicit ORDER BY in the outer query so that we no longer need
to disable derived_merge optimizer.
c.f. https://bugs.launchpad.net/maria/+bug/985828

- group_by, group_by_expression -> group_by_list
- select_list, select_expression -> select_dict
- sort_on, sort_on_order, order_by_expression -> order_list

It is useful when use select_expression in inner query and use
group_by_expression or order_by_expression in outer query.

Revert "Add auto_extend_select_list argument in buildSQLQuery() and use alias in group_by_expression and order_by_expression."
Revert "Support group_by_list and order_by_list in WebSection_getDocumentValueList."
Revert "Support order_by_list in Resource_zGetMovementHistoryList."

No need to extend SQLCatalog parameter to support group_by_list and order_by_list in sub-queries.

It should be only for the case where no predicate criterion exists at all.

forge: do not link to Bug portal_type base categories that are already provided by Bug property_sheet

Added in keep path list, for compatibility