Export and use core-database-postgres typedefs

[paroxysm]

Proposed changes

resolves #1791

This refactor has exposed some strange design decisions made. There's some methods that are on the postgres implementation of the Connection interface that can be moved into an abstract class.
PS. We probably should break out the business logic in Connection out into Services that leverage the connection and repositories so we're separating concerns

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improve a current implementation without adding a new feature or fixing a bug)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Build (changes that affect the build system)
• Docs (documentation only changes)
• Test (adding missing tests or fixing existing tests)
• Other... Please describe:

Checklist

• I have read the CONTRIBUTING documentation
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[faustbrian]

The mentioned issues will be taken core of by #1573. There is still a lot of old code in it written by someone else that will refactored.

In the end the core-database-postgres package will barely overwrite anything and mostly just provide data to the underlying core-database package. That package will then pass the data on to services that specifically handle blocks, transactions, rounds and wallets to clearly separate behaviour and make code SOLID as time goes on now that we finally ditched JavaScript.

There is tons of refactoring and especially improvements to the plugin system and structure in the pipeline now that JavaScript is gone but that will take time.

[faustbrian]

@paroxysm conflicts

[paroxysm]

@faustbrian Great! There's definitely some tech debt that needs to be addressed

[paroxysm]

@faustbrian I've addressed the conflicts.
I purposefully left out core-graphql because it was referencing some methods that the PostgresConnection class doesn't define.
I'll need to track those down and formally declare them