Issues 305: don't overescape strings at extraction time

* We now only escape single quotes at extractions and leave other special characters alone (&\<>")
* We escape special characters at display time
* Utils::cleanSearch() renamed to Utils::cleanString() and no longer sanitize strings for security (use Utils::secureText())
* Searches for special characters such as &brandshortname; or \ now work, same for API
* Google and Bing links no longer include html entities
Do you have an example at hand? Wouldn't it be a single slash (e.g. ```\'```)? Also, the last ```\\\\``` look to have too many slashes.