Properly catch PlacesException$OperationInterrupted

[Mugurell]

There's a recent spike in handled exceptions reports for PlacesException$OperationInterrupted following #12469

It was expected that this would happen but while the current approach would try to catch the exception as stemming from the interrupt call upon more investigation it seems like the actually interrupted operation will throw and only if the query was in progress, and in this scenario the exception is caught and reported because it was unexpected.

As a solution the try catch blocks should be combined with the handlePlacesException alson expecting the PlacesException$OperationInterrupted exception and not reporting it to the crash services.

┆Issue is synchronized with this Jira Task

[Mugurell]

Verifying in Sentry we see that:

• there are tens of thousands of reports from the build from July 28th - https://sentry.io/organizations/mozilla/issues/?query=PlacesException%24OperationInterrupted+ac.version%3A105.0.20220728143105&statsPeriod=14d
• no reports from the build from July 30 - https://sentry.io/organizations/mozilla/issues/?query=PlacesException%24OperationInterrupted+ac.version%3A105.0.20220730143045
• no reports from the build from July 31st - https://sentry.io/organizations/mozilla/issues/?query=PlacesException%24OperationInterrupted+ac.version%3A105.0.20220731143130
• no reports from the build from August 1st - https://sentry.io/organizations/mozilla/issues/?query=PlacesException%24OperationInterrupted+ac.version%3A105.0.20220801222259

So looks like the issues was indeed resolved.