FilterChooser does not support fields with display names that include words in reg exp list

[saba-mo]

If the filter chooser model includes a field where the display name includes a certain word (like, not like, begins, ends, is), the query incorrectly spilts the display name and results in the wrong field name. This was seen in a client app where the display name that started with "is" appeared in the filter chooser's options, but selecting it led to the "No matches found" message. See QueryEngine's getDecomposedQuery method.