feat: Metricflow and dbt Core

[betodealmeida]

Add support for Metricflow when using dbt Core sync.

Ran:

$ preset-cli --workspaces=https://49437123.us1a.app.preset.io \
> superset sync dbt-core ~/Projects/github/jaffle-sl-template/target/manifest.json \
> --project=jaffle_shop --target=dev

See datasets and metrics in https://49437123.us1a.app.preset.io.

Will update tests.

[shortcut-integration]

This pull request has been linked to Shortcut Story #79017: Support for metrics definition in dbt Core 1.6 with the CLI.

[Vitor-Avila]

This is awesome!!!

[Vitor-Avila]

Followed below steps to test these changes:

1. Created a new PSQL DB.
2. Cloned this template repo: https://github.com/dbt-labs/jaffle-sl-template.
3. Add the changes from this PR to avoid errors: Fix errors occur on mf validate-configs dbt-labs/jaffle-sl-template#62.
4. Configured the DB connection to the new PSQL DB.
5. Replaced DATETIME in the configs with TIMESTAMP (sice I'm using Postgres rather than Snowflake).
6. Followed the steps outlined in the repo README to set up the dbt environment.

[Vitor-Avila]

Now the CLI requires having metricflow installed to properly retrieve the SQL syntax for metrics. I wonder if we can identify the error returned in case it's not installed (maybe something like command not found and provide an error to the user instructing to install the package. We could raise it as an error to make sure a CI job would also show as failed so the user adds the specific metricflow package (according to their engine) to their configurations.

We could also add the package to the list of requirements.

[Vitor-Avila]

I'm working on this PR #266 and could potentially further improve it to also list at the end of the execution any failed metric (according to the limitations we currently have).

[Vitor-Avila]

Thank you so much for working on this! I left some non-blocking comments.