Update how we store count data - make it "resistant" to db-truncations

[123FLO321]

Description

This PR updatest how count data is stored. Now data is stored permanently independent on whether or not the db gets truncated. Works the same way the raid detection works.

Motivation and Context

With this PR we can truncated the pokemon table without losing count data.

How Has This Been Tested?

Local instance but needs further testing.

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

[michikrug]

Please describe you changes more clearly, since we already store the count in a file.

(I get what you are aiming for, but please help others to do so too ;))

[Obihoernchen]

anybody tested this one?