way it's exported / imported and tested.

a new bt5 (erp5_security_uid_innodb_catalog) upon installation.
Add all generic ZSQL methods to this new bt5
so projects can adjust only the minimum required.

need to change catalog as this can be quite time consuming.

Adjust tests as local roles structure changed.

Avoid to catalog some special roles like Owner (defined in getSQLCatalog().getSQLCatalogRoleKeysList()).
As __ac_local_roles_group_id_dict__ changed its structure to 'local_group_id': ['Role'] (just the opposite)
adjust test as well.

not pollute with more than required rows table roles_and_users.
As result this will increase a bit object database.

Try to support migration of old instances (containing old erp5_property_sheets)
with recent products. This is especially visible with BusinessTemplate property sheet
when new filesystem versions require an up to date erp5_property_sheets bt5 which itself
can not be installed.

a bit modify previous commit ba435293, use untouched message for default, and explicitly convert to unicode for non existing case.

support non-ascii msgid and add a backward compatibility for the existing catalog that stores non-ascii msgid as str not unicode.

  * to_str does not return str result
  * typo in variable name

call activate() in the same transaction otherwise we may get lots of UnsupportedWorkflowMethod errors.

Also, use local imports of itools where this is still necessary,  and remove all mention of itools from ERP5 code.

Instead of itools.gettext

Remove files/functionalities not needed by ERP5

Fork from master branch of Localizer and 0.50 branch of itools into ERP5

Remove almost everything from itools except bare essentials needed by a stripped Localizer for ERP5

Follow up the commit 4b16e1dd (use UnrestrictedMethod's super user instead of ad-hoc SUPER_USER.)