refactor: implement repositories

[7mochi]

• Logs refactor: logs repository #484
• Map requests refactor: map_requests repository #485
• Comments refactor: comments repository #486
• Mails refactor: mails repository #487
• Ingame logins refactor: ingame_logins repository #489
• Client hashes refactor: client_hashes repository #595
• Favourites refactor: favourites repository #598
• Map ratings refactor: ratings repository #599
• User achievements
• Tourney pools Split MapPools and related collections/cache into repositories #597
• Tourney pool maps Split MapPools and related collections/cache into repositories #597
• Players
• Channels
• Clans
• Matches
• API keys
• User Relationships

[NiceAesth]

What is the direction you are going with the repository PRs? I see you changed the branch for them

[7mochi]

What is the direction you are going with the repository PRs? I see you changed the branch for them

I wanted to make another PR with all the repositories implemented nvm

[cmyui]

I've created this PR as a reference for breaking up the collections modules, as they may be a bit trickier than usual:

• Split MapPools and related collections/cache into repositories #597

This PR's description breaks down how we might approach players, channels, clans and matches similarly.

[tsunyoku]

just adding a note onto this about us refactoring existing repositories to sqlalchemy core (for query building), any further repos should be made in the same manor (use #632 as a good example of pretty much any usecase you might run into when writing the repos)