[HUBBLE 465] Migrate dbt project evaluator and tests to Github Actions

[eduardo-nercolini]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with the jira ticket associated with the PR.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated the docs and the README with the added features, breaking changes, new instructions on how to use the repository.

Release planning

• I've decided if this PR requires a new major/minor/patch version accordingly to
  semver, and I've changed the name of the BRANCH to release/_ , feature/_ or patch/* .

What

This PR add dbt project evaluator package to run on GitHub Actions.

Why

Misconfiguration are not caught until code is merged to the master branch since these steps only run during the jenkins pipeline. Migrating the dbt build actions to GitHub actions allows to enable ci/cd to the internal repo, and ensure bad code does not get merged to the master branch.

Known limitations

N/A

[sydneynotthecity]

LGTM

[sydneynotthecity]

Are the disabled checks for dbt_project_evaluator due to the current problems with the dbt Jenkins build? Is the intent that these checks will always be disabled, or is this temporary until we get the build working again?

[sydneynotthecity]

Answer: these will always be disabled unless we decide to increase the quality checks by the project evaluator.