Catch and handle errors if getOptionsFull fails

[Kuuuube]

Fixes #723

I think this issue is due to calling triggerDatabaseUpdated without an await before _addDictionarySettings causing a race condition. But due to the nature of this bug there's no way to be 100% sure.

Simply awaiting triggerDatabaseUpdated doesn't work due to it calling ensureDictionarySettings conflicting with _addDictionarySettings and creating duplicate dict settings. (ensureDictionarySettings makes sure all dicts have settings entries and adds one if it is lacking. _addDictionarySettings adds a setting regardless of whether one exists already.)

Running triggerDatabaseUpdated after _addDictionarySettings appears to work perfectly fine.

I've also allowed getOptionsFull to retry up to 10 times if it fails, catching any errors so the dict import process is not interrupted.

At a minimum these fixes will make it so firefox users don't have to worry about the dict import process randomly breaking when importing multiple dicts and requiring manually restarting the import. But hopefully this will entirely eliminate settings related errors for firefox imports.

[jamesmaa]

Why would getOptionsFull be flaky?

[Kuuuube]

Not sure, it seems to be fine elsewhere but there's been a decent amount of reports about it breaking in this particular spot and I was able to replicate it.

This also only happens on firefox so it's probably safe to say it's a browser related bug. Easy enough to work around on our end though.

[Kuuuube]

Also could be something related to updating the database right before fetching options. There arent many places that happens.