These are the easy uses, there are more to come.

Eventhough diff is large, this commits just removes the default_params
TALES.

`hide_grouping` has no effect here.

git grep -l ERP5Site_getAuthenticatedMemberPersonValue | xargs sed -i 's!\.ERP5Site_getAuthenticatedMemberPersonValue()!.getPortalObject().portal_membership.getAuthenticatedMember().getUserValue()!g'
Plus s/portal.getPortalObject()/portal/g where modified by above regex.
Plus manual edits of the few remaining matches.
Special mention for DiscussionThreadModule_addReply, which forgot to
actually call the script.

To prepare for moving user id to a different property.
Mostly replacing getReference on Persons with Person_getUserId, and
catalog searches with PAS API when it is meant to search for a user and
not really a person by reference.

Allows being compatible with future, improved PAS plugin features.
Also, drop a few useless imports.

We should have done before committing 76ecef89
but doing it now with a dummy merge also works.

Unfortunately, this is not really useful for blame, because all lines are
rewritten, at least to remove the trailing '\n'.

Files that have already been modified in 'master' branch are excluded.

All business templates migrated to new format with files like Python Scripts, Web Pages, Web Scripts etc. separate to xml

It includes the following bt5 :
  erp5_property_sheets: replace the journal category in Movement by the ledger category
  erp5_configurator_standard_trade_template: replaces the base category journal by ledger in simulation rules
  erp5_project: replaces journal base category by ledger
  erp5_research_item: replaces the journal base category by ledger
  erp5_mysql_innodb_catalog: replaces queries containing journal by ledger

because it is called from unrestricted method : builder._searchMovementList().

deprecated movement table was used

This reverts commit 0fc02acc.

selection_report is actually a legal ZSQLCatalog parameter.
selection is not, but there are more instances of its usage, so cleanup
will be in a separate commit.

Items are used on tasks for generating reports

This is useful for some reporting

The new approach is a script named ERP5Site_getWorkflowStateItemList that receives the portal type and the state variable (simulation_state/validation_state) as parameters and it will returns the states for the workflow chained to the portal type. This way all the standard dialogs works out of the box even if you customize a workflow chain

-Titlecase terms, uppercase abbreviations, avoid jargons, add titles to empty title forms....