feat: postgres integration - create database

[gaurav274]

1. Add support for creating database

CREATE DATABASE db
WITH ENGINE = "postgres",
PARAMETERS = {
    "user": "user",
    "password": "password",
    "host": "127.0.0.1",
    "port": "5432",
    "database": "demo"
};

2. Persist the info in the catalog
3. Todo: Verify if the provided info is valid - next PR

[gaurav274]

@xzdandy @jiashenC Added a skipping behavior in the system to avoid having to write boilerplate code for binder, optimizer.

[xzdandy]

Looks good to me. To make it clear, the default engine (for now, sqlite3) in evadb/catalog/sql_config.py will not have an entry in DatabaseCatalog (otherwise, we have a loop. Maybe we can actually, so it is not treated differently with any other databases created later by the user).
Some decisions we need to think are

• Is the default engine only storing EvaDB's metadata or it can also store user's data? In other words, can user use the EvaDB without connecting to any other structure databases?
• Is the default engine always local or it can also connect to a remote database? Sharing model and external database connection with other users.

[xzdandy]

The Test | v3.10 | Linux | Postgres test actually failed. Need to take a look.

[gaurav274]

Looks good to me. To make it clear, the default engine (for now, sqlite3) in evadb/catalog/sql_config.py will not have an entry in DatabaseCatalog (otherwise, we have a loop. Maybe we can actually, so it is not treated differently with any other databases created later by the user). Some decisions we need to think are

• Is the default engine only storing EvaDB's metadata or it can also store user's data? In other words, can user use the EvaDB without connecting to any other structure databases?
• Is the default engine always local or it can also connect to a remote database? Sharing model and external database connection with other users.

Will document it in our design docs