Refactor search providers

[zoran995]

What this PR does

Fixes #

During testing the search providers, I discovered that search debounce doesn't work correctly and that we can achieve a better UX when autocomplete is disabled for some search providers.

Before:

• Try entering more than three characters in the search box and observe that the search is triggered on each change
• Try searching for mel\ and observe a white screen due to an unescaped regex group

After:

• When autocomplete is disabled for some search providers, an info message for it is shown saying "Press Enter to start searching"; other search providers will search with autocomplete
• Search is debounced correctly, and the logic is moved to the search provider mixin level
• After the enter is pressed, it will start manual search, bypassing the debounce mechanism.
• Search string is escaped for highlight, resolving the hard error thrown due toan unescaped group
• Fixed a few potential issues with map credits for search providers

Test me

How should reviewers test this? (Hint: If you want to provide a test catalog item, create a Gist of its catalog JSON, add its url and your branch name to this url: http://ci.terria.io/<branch name>/#clean&<raw url of your gist> , and then paste that in the body of this PR)

Checklist

• There are unit tests to verify my changes are correct or unit tests aren't applicable (if so, write quick reason why unit tests don't exist)
• I've updated relevant documentation in doc/.
• I've updated CHANGES.md with what I changed.
• I've provided instructions in the PR description on how to test this PR.

[na9da]

Why override this here when it is already part of LocationSearchProviderTraits and is defaulting to true? Same for the other providers.

[zoran995]

I just wanted to be explicit for all search providers, I can remove it if necessary

[zoran995]

Actually I was running into a bug that the value wasn't propagated correctly

[na9da]

Doubt: Could you explain when manuallyTriggered is true and why we need to differentiate both?

[zoran995]

manuallyTriggered is when the user presses enter to start the search; in that case, we need to cancel the debounce and run the search without waiting

[na9da]

This should be catalogSearchProvider.searchResult instead (currently this results in app crash when searching from catalog explorer modal)

[na9da]

BTW, there is a new RegExp.escape, although it is pretty new.

[zoran995]

I would avoid moving it for some time, as it is still pretty new although it would work for most of the users, and this is enough to resolve the issue we are currently seeing

[na9da]

@zoran995 - Looks good, just a few comments.

[na9da]

Search from mobile view must also be fixed.

[zoran995]

@na9da this is ready for another pass, #7715 builds on top of this