This change comes as a result of some user feedback and some of my own experience as I've been using repositories in code

The original intent of a repository method was to make it as intuitive and simple to use as possible so the generation made assumptions about what database pointer it should use under the hood database or content_db.

This all works fine and dandy, however this pattern breaks down as soon as we want to use a repository in any shared ./common logic. The reason for this is our poorly distributed Database logic. For world and zone we have separate classes tied to pointers database and content_db so we cannot use shared type signatures and make assumptions within the repository methods

For this reason, these assumptions and attempts to simplify usage of repositories are outweighed by the annoyances of not being able to use them in any ./common shared logic which is a very common use case

This PR implements explicitly passing in database pointers into repository methods and updates all of the referenced places in the code where its used