Over the years, we included almost all possible default group by criterions for getMovementHistoryList, so that in essence, we do not group ... for example, we did 7814c521 . It would be better for performance and more logical to just not group by at all, getMovementHistoryList should just return the list of movements.

This is still possible to use explicit group by parameters in getMovementHistoryList, for example grouping by [explanation_uid](https://lab.nexedi.com/nexedi/erp5/blob/c413d34b9d5db0beda2b9540d563529082855d91/product/ERP5/tests/testInventoryAPI.py#L2416) like we can do in [some accounting reports](https://lab.nexedi.com/nexedi/erp5/blob/c413d34b9d5db0beda2b9540d563529082855d91/bt5/erp5_accounting/SkinTemplateItem/portal_skins/erp5_accounting/AccountModule_getGeneralLedgerReportSectionList.py#L111).

I don't have a proper benchmark, but on the instance where we discover the issue, a simple getMovementHistoryList yieliding 112301 results went from several minutes spent in state *Removing duplicates*  (I killed the query after some time) to about 3 seconds.

cc @vpelletier @jm @gabriel 

/reviewed-on nexedi/erp5!171

http://dhtmlx.com/docs/products/dhtmlxScheduler/ integration for ERP5

Use "Transaction Type" everywhere and stop using "Journal Type".

On accounting transaction views, it is "Transaction Type".

In l10n_fr, l10n_de, l10n_pl both "Journal Type" and "Transaction Type"
where translated to the same term.

This cause slow queries and returning rows that user won't be able to
group because we only allow to group transactions from the account
anyway.

because credential_request.submit() is now guarded by Modify portal content permission.

ProgrammingError could be raised for various raisons, while the code
was assuming that the only raison was missing table. Improve by making
sure the error is about missing table, if not, raise.

Left panel should not be always visible on a laptop screen

expr(md) raises NameError when expr references a non-given argument, so
catch that exception too. (sqlvar catches Exception, which seems overkill,
so don't follow it)

Fix missing import.
Actually follow sqltest render API, which is different from sqlvar's.

mrp simulation: allow to customize transformation rule to define to reverse input source/destination

Somehow two files didn't made it to the recent deploy. I am still to figure out the reason but I suspect it might be due to my recent rebase.

/reviewed-on nexedi/erp5!166

- use mixin class to allow reusing common performance functions
- remove usage of quiet and run_all_test

Reduces the number of meaningless 404 errors.

so that we keep the query string in the redirect url if exists.