ENHANCEMENT overload getResults() with extension point to change $booleanSearch param

[muskie9]

resolves #22

[fonsekaean]

@muskie9 can you explain whats the issue we are trying to solve here?

[muskie9]

@fonsekaean sure, and in all honesty it's more so something that should probably go into CMS vs this module.

I ran into a situation where searching a keyword that has - in it does not yield the expected results due to IN BOOLEAN MODE being set in searchEngine() from the passed param. This param is set in the SearchForm::getResults() method and relies on checking for 4 particular operators that are used for IN BOOLEAN MODE. These modifiers have special meaning at the beginning or end of words in the search string.

With the module already overriding SearchForm from CMS it was seemingly a lower barrier to open a pull request vs the CMS process. The getResults() method added in this pull request adds an extension point allowing for setting the param that affects the IN BOOLEAN MODE being included in the query. I still plan on raising a ticket in CMS to see if it's something that would be accepted but I figured others may find this useful in the meantime if using this module.

Hope that sheds some light on the issue and solve. No worries if it's something you'd rather not have in the module.