Periodically sync database to the drive

[lantiga]

What does this PR do?

Currently the database component syncs to the drive on_exit, which will also be triggered in case of an exception. In order to further ensure that data is not lost in case of an unhandled crash, this PR introduces periodic sync'ing of the database with a set time interval.

Does your PR introduce any breaking changes? If yes, please list them.

None

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

cc @Borda

[Borda]

What will happen if the sync process takes longer than the interval?

[lantiga]

What will happen if the sync process takes longer than the interval?

The copy and the interval are sequential and all calls are blocking, so the interval indicates how much time will elapse before a new copy is performed.

[tchaton]

Nice addition !