Adopt sqlite with proper caching

[ppfeister]

Description

• [ ] Switch from text files for each username to a single sqlite database
• [ ] Allow for text file output as an option to better support legacy?
• [ ] Properly cache and expire results in database (only cache positive hits)

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[sdushantha]

I like your suggestion @ppfeister, it prevents having several .txt files scattered across the file system.

With the results being stored in a sqlite DB, would we add a few extra flags Sherlock so that i can list and remove results from the DB?

[ppfeister]

Proper implementation in my mind would require results to be cached for a standard amount of time (TBD), allowing the result to be overwritten when expired (reduce rate limit hits), with a flag to skip caching new entries, and a flag to ignore presently cached entries.

Say, --no-cache and --force-check or similar.

I didn't see a need for any further options to manipulate the db, but if any should be added for better UX, they should be behind a sub-command of some type rather than even more flags than we already have. Say, sherlock cache --clear and sherlock cache --clear-site or similar. Only issue this specific example raises is ambiguity between cache the command and cache the username, but something similar should be workable.

[ppfeister]

sherlock-cache likely to be added.