Fixes T12596. A query for a token (like "having") which stems to a stopword (like "have") currently survives filtering. Stem it first so it gets caught.

Also, for InnoDB, a custom stopword table can be configured. If it is, read that instead of the default stopword list (I configured it locally, but the default list is reasonable so we never formally recommended installs configure it).

Queried for words that stem to stopwords, saw them filtered:

Queried for the original problem query and saw "having" caught with "have" in the stopword list:

Fiddled with local InnoDB stopword table config and saw the stopword list get loaded correctly.