Putting field in center increases the string field size for ERP5JS

re-apply 25cd1201 that was mistakenly reverted by b847b45e

Hey @Nicolas can you please take a look at all this ?

All this started when I realised we probably do not want to allow grouping reference to be set when we have transactions from different ledgers ( edda8b58 ) and then realized it would be required to allow choosing ledger in grouping fast input instead of just showing all ledgers together ( d1ecbe29 ).

The rest are small changes to move out complex logic from TALES to a script and small fixups.

Thanks

/reviewed-on !170

This reverts commit b847b45e, reversing
changes made to 9075a38f.
The reverted commmit has been done automatically, investigation is needed

Putting field in center increases the string field size for ERP5JS

We were just testing that grouping references are automatically set. It
is better to also check they are set to the same thing.

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

and rely on Base_getPreferredCategoryChildItemList to have results
sorted and displayed according to user preferences.

and use it instead of repeating that logic in field libraries

Add missing metadata for delivery type view

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)