Boolean OR sometimes matches literal *or* e.g. in 'order'

[jnweiger]

Seen with search_elastic 2.4.0-RC.1

Config variable occ config:app:get search_elastic connectors_search is unset. Or, same results with: occ config:app:set search_elastic connectors_search --value "RelevanceV2"

• Type into the search field and hit enter: features workstation
• five results appear, with one of the two words, or both. OK.
• insert OR between the words, so that the search reads features OR workstation
• still the same 5 results. Boolean OR seems to be the default. OK.
• delete the search field, type the entire expression in one go: features OR workstation
• 7 search results appear, also finding literal or and also order in my case. BAD

Testing with AND:

• delete the search field, type into the search field and hit enter: features workstation
• five results appear, with one of the two words, or both. OK.
• insert AND between the words, so that the search reads features AND workstation
• still the same 5 results. The boolean operator AND is ignored. BAD
• insert NOT after AND, so that the search reads features AND NOT workstation
• Now 7 results appear, the Boolean operator AND NOT is taken as literal words. BAD

Expected behaviour:

• the results should not depend on how text was edited in the seach entry.
• When the same string is in the field, the result sould be the same.
• AND, OR, NOT should either always be normal search terms, or always work as boolean operators.