erp5_full_text_mroonga_catalog: remove erroneous Keyword Search Keys

While investigating MariaDB slowdown, I noticed that some Keyword Search Keys,
ie. keys triggering search by `LIKE` instead of strict equality, were
incorrect. This seems to come from a change that happened upstream. In any
case, they can safely be removed already.

bt5/erp5_full_text_mroonga_catalog/CatalogSearchKeyTemplateItem/search_key_list.xml

-<key_list>
- <key>SearchableText | MroongaBooleanFullTextKey</key>
- <key>catalog_full_text.description | MroongaBooleanFullTextKey</key>
- <key>catalog_full_text.title | MroongaBooleanFullTextKey</key>
- <key>full_text.SearchableText | MroongaBooleanFullTextKey</key>
-</key_list>
\ No newline at end of file

bt5/erp5_full_text_mroonga_catalog/bt/template_catalog_search_key_list

-SearchableText | MroongaBooleanFullTextKey
-catalog_full_text.description | MroongaBooleanFullTextKey
-catalog_full_text.title | MroongaBooleanFullTextKey
-full_text.SearchableText | MroongaBooleanFullTextKey
\ No newline at end of file

[Xiaowu Zhang]

@tsoulard do you have an example query before and after this commit ?

[Titouan Soulard]

Oooh interesting this one, nice that you bumped me, seems I committed in the wrong file. What I wanted is committed nowhere (can be, but isn't). This looks like an upstream bug, so I will investigate upstream, this file seems the root cause but there might be a bug in Business Template processing, or default configurator.

So if you want to know the problem, it is simply invalid configuration, I do not think it is causing issues I just took notice while looking at the catalog's configuration. The old configuration looked like this:

Where you can see the ???, indeed indicating a wrong configuration since the parser does not care about this pipe. But once again, this is not the right file to commit in, so you may undo the change. Production does not care about this file anyway, since catalog configuration is not reprocessed from BT5 on upgrade.