Include support for postgres

[apotek]

Description

Currently the plugin only supports mysql/mariadb databases. How can we abstract the code in order to more flexibly support other db engines. We start with one: postgres, and the abstraction required to support it should get us into a place where this can then more easily be expanded into other database engines.

Issue Owner

@apotek

Acceptance Criteria

Transparently be able to invoke ddev dblog on|off|tail with postgres using a minimum of conditionals (or none) in the code.

Tests should be able to be run successfully for mariadb/mysql/postgres

Proposed Solution

A user should be able to install and invoke dblog without caring which database is actually installed.

• Probably we will use the environment to define the kind of engine
• Probably we will create functions or includes for capturing the log state and for setting the log state, which can dynamically be invoked.