Bugfix FXIOS-5344 [v109] fixes search highlights getting interrupted

[tarikeshaq]

Bugfix for #12530

Moves the places.interruptReader() to only run if search highlights are disabled and we are running the new places history. The interrupt helps make sure we aren't running too many long-running queries back to back against places.db without interruption.

Additionally, optimizes the search highlights case. Previously, we would always run the normal history query, but then discard its result if search highlights are enabled. Now, we only run the search query if search highlights are disabled.

Some more context on the bug in the issue.

Possibly for a follow-up:

• We should also interrupt the reader in the case of history highlights by introducing an interrupt in the search highlights flow
• Even better, but more complicated, the search highlights should probably have their own reader connection. We have lots of logic in application-services that serves the case of multiple readers. We can have a reader per use case. (this becomes more important once we use AS history)

cc @lmarceau @badboy

[lmarceau]

Build was green here