Feature/db update

[fanno]

Feature tests if the cache and downloaded version has the right structure before using it and storing it.

we have discussed if the cargo container should have a hash EG a MD5 to check that vs the downloaded version as a first step verification.

options added to chose update rate and do a manual update

few more options added to the in page notification (maybe they should be filtered further back so they would also not trigger browser notification?)

---

• The target of this PR is the main branch.
• No commits are missing from forked base branch (e.g. modified main branch instead of dev)
• You have squashed commits that might be considered: 'noisy' or partial, e.g. not candidates for cherry picking
• All test pass, run npm test
• The code is formatted, run npm run format
• You have updated or added test cases, as/if required
• You have installed and tried out the plugin in a supported browser

[fanno]

Let me know if there is anything that need to be changed