- Two methods defined twice with the same code in the same script

* to quickly setup catalog_full_text table, you can use the following SQL.

  REPLACE INTO catalog_full_text SELECT uid, title, description FROM catalog;

* non fulltext queries like '=abc', '>abc', '%abc%' are supported.

* now erp5_full_text_mroonga_catalog is used for unit tests thus I recommend using it instead of erp5_full_text_myisam_catalog.

* to migrate existing MyISAM full_text table into Mroonga, you can use the following SQL.

  ALTER TABLE full_text DROP KEY SearchableText,
    ENGINE = mroonga,
    ADD FULLTEXT KEY SearchableText (`SearchableText`) COMMENT 'parser "TokenBigramSplitSymbolAlpha"';

* fulltext search score is no longer provided as (column_name) but now provided as (column_name)__score__.

* (category)_title, like source_title, related keys are automatically generated. (category)_description keys as well.

  This parameter has been passed always by the erp5.util implementation. Introduce
  this parameter makes the API compatible for future implementation with support
  to scalability tests even if the current code is not ready yet.

Optimize sorting of list of test suite to be executed by test nodes.
We give priority to test suite with older test results. This allows
to have test node resources in a more fair way.

Conflicts:
	bt5/erp5_test_result/bt/revision
	bt5/erp5_test_result/bt/template_document_id_list
	bt5/erp5_test_result/bt/template_extension_id_list
(cherry picked from commit 63c1fc096663f6c96ab61e5acebe2dcbe801dfa5)

Conflicts:

	bt5/erp5_test_result/TestTemplateItem/portal_components/test.erp5.testTaskDistribution.py
	bt5/erp5_test_result/bt/revision