Consider combining database package into usher server

[mikelax]

Feature Overview

As The Usher project stands today, we currently have two deployable packages that comprise The Usher, there is the actual server project and a separate database package. The server has the database package as a dependency.

I would like to propose that we remove the separate database package and combine the database source code into existing server package.

Describe the solution you'd like
The original idea for two separate packages was to decouple the database from the server, and allow for the use of different database engines. The idea was that this would be done by "re-implmenting" a different database package and have the server use that as a dependency.

In practice I don't think we will ever get to this point, nor do I think this is actually the direct that we want to go. There is way too much logic that is now being built into the database source code to allow / require someone to "copy / paste" for a different db engine.

The current setup is also difficult to work with as a developer, as we are currently not taking advantage of best practice programming practices, ie. for error handling we are returning values instead of throwing exceptions.

I think the better approach would be to have a single database codebase, and allow for just the "database env / driver" to be configurable for any supported database engine. This would require a user to just provide the correct database connection and environment values, not re-implement a full codebase.

Additional context

Add any other context or screenshots about the feature request here.