Conflicts:
	bt5/erp5_accounting/bt/revision
	bt5/erp5_base/SkinTemplateItem/portal_skins/erp5_base/Entity_sendEmail.xml
	bt5/erp5_base/SkinTemplateItem/portal_skins/erp5_base/Event_send.xml
	bt5/erp5_base/bt/revision
	bt5/erp5_bearer_token/SkinTemplateItem/portal_skins/erp5_bearer_token/Person_getBearerToken.xml
	bt5/erp5_mrp/bt/template_portal_type_workflow_chain_list
	bt5/erp5_promise/SkinTemplateItem/portal_skins/erp5_promise/Alarm_checkPromiseConversionServer.xml
	bt5/erp5_trade/WorkflowTemplateItem/portal_workflow/packing_list_workflow/scripts/PackingList_updateAppliedRule.xml
	bt5/erp5_trade/bt/revision
	bt5/erp5_web/bt/revision
	product/ERP5/bootstrap/erp5_property_sheets/bt/revision
	product/ERP5Type/Base.py

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.

do not use birthday property in Credential Request or Credential Update, because its storage is start_date and start_date has different meaning in these portal types. add assertions to check if birthday is set by credential request, and not updated unexpectedly by credential update.

clean up reportPaymentStatus function on PaypalService to call PaypalService_reportPaymentStatus script regardless of the outcome of the status and through the activities and added one test to cover this method

Fix unit test

(cherry picked from commit 583d5b149312d7c4cd45e58bc1793fc02722f559)

This reverts commit ae1a45e4.

Test runners are not able anyway to use pure in-ZODB tests.

(cherry picked from commit e7967448c588f4b5743dfca28d9be3ab47ba05c9)

Conflicts:
	product/ERP5Type/dynamic/component_package.py

Followup of a29456bc.
(cherry picked from commit f73c1f57962f275246da0e125ceb4f312e0399fb)

(cherry picked from commit 7af4728b7463a521fadca3dcedbd5e445d9ef12e)

(cherry picked from commit 3fa79d0e6f1a771caae0f898e87e015486180975)

Revert "clean up reportPaymentStatus function on PaypalService to call PaypalService_reportPaymentStatus script regardless of the outcome of the status and added one test to cover this method"

This reverts commit 03e358bc.

One test was failing

clean up reportPaymentStatus function on PaypalService to call PaypalService_reportPaymentStatus script regardless of the outcome of the status and added one test to cover this method

use the interpreter's import lock instead of threading.RLock in ERP5Type.dynamic to avoid possible dead lock.
(cherry picked from commit a29456bc)

Sometimes on configuration product-config can be defined but promise-path and
site id isn't, like for example when some instance use DeadlockDebugger.