While installing a BT5 make sure not to install duplicate keys for the following ZSQLCatalog properties:
 - sql_catalog_search_keys
 - sql_catalog_related_keys
 - sql_catalog_scriptable_keys
 - sql_catalog_role_keys
 - sql_catalog_local_role_keys

Remove code duplication and make it easy to override how the key should be modified at install time.

Noticed by Kazuhiko.

If socket timeout is not set the call can never receive a response and
system become locked for ever waiting a reply from task distribution server.

Path https://svn.erp5.org/repos/public/erp5/trunk/utils/timing_log_parser/plot.py, revision 46030.

Path https://svn.erp5.org/repos/public/erp5/trunk/utils/timing_log_parser/parse_timing_log.py, revision 34836.

Fixes test results containing values from unrelated tests, and occasional
"NoneType has no attribute stop" errors.

This change will permit "clean up" scripts remove certain objects created
by "zope" user, which is typically the default user on instances.

This is just a quick fix, later this value should be collected automatically,
or using promise parametes.

Allow to specify an expected transition message when submitting a workflow even if there is no dialog.

Mark three tests as expected failure. To filter by category with full inventory document does not work.

- Avoid to create too much OIDs when updateLastMaxIdDictFromTable
- Add a parameter 'id_group' into IdTool_zGetValueList for the
  scalability of updateLastMaxIdDictFromTable().
  This parameter is intended to use with CMFActivity
  (see TestIdTool.test_08_updateLastMaxIdDictFromTable).

This method is intended to use when we are disabled 'Store in the ZODB'
or set a big number as the 'Store interval', but at the same time we need to
update the persistent dict from the fresh portal_ids table at a certain point.

This method needs a unit test.

So that we can get all the records of portal_ids table even when there are more
than 1000 id_group on the table. The ZSQLMethod was not intended to limit to
retrieve the records.
Of course it is better to get the records more gracefully like first getting
0..999, then 1000..1999. For now this is acceptable.
(Confirmed by Sebastien)

This test will make sure that getInventoryList works in the situation which two sections use the same node and one section has full inventory for the node.

Do use catalog when switching between different tabs to avoid having to deal with objectValues / contentValues API. Avoid use cases when a Pad may contains many Boxes.