Switch to Postgres storage

[alfiedotwtf]

This change switches out the storage API for the Scanner and Web Server from InMemory to Postgres

[TheQuantumPhysicist]

Please make an attempt to group postgres-related configuration to in its own struct. I think clap supports composable configuration, not sure though.

Please note that we DO NOT want use commands for this. I know commands can do it, but it's the wrong tool. It would be sufficient to just be able to put these in a struct then throw the struct in here.

IF that works, then it would be great if we could have tree-like validation, where postgres settings only work if the database type is postgres. But that comes later, no need to spend too much time on it. Let's start with the struct.

If that struct works, then please put it in api-server-common, and use it for both the scanner-daemon and the web-server.

[alfiedotwtf]

The new changes have a separate struct for Postgres, and are parsed via the default(). If we want to be optional vs other backing storage types as discussed in the meeting, I'm not sure if Clap supports the Enum like you mentioned so you may have to detect manually after parse() the top-level?

[TheQuantumPhysicist]

I can live with how it's now. We can beautify it later.

[OBorce]

If you want to use an enum you can actually use a subcommand like:

mintlayer-core/node-lib/src/options.rs

Lines 44 to 52 in e3c8196

	#[derive(Subcommand, Clone, Debug)]
	pub enum Command {
	/// Run the mainnet node.
	Mainnet(RunOptions),
	/// Run the testnet node.
	Testnet(RunOptions),
	/// Run the regtest node.
	Regtest(Box<RegtestOptions>),
	}