Add support for "Config" select/exclude to DbtDag & DbtTaskGroup parsers

[chrishronek]

Closes 90

I added the label bug because I found syntax preventing tags from being read out of properties.yml files correctly.

[chrishronek]

This will convert the DbtModelConfig to this:

DbtModel(name='orders', path='dbt/jaffle_shop/models/orders.sql', config=DbtModelConfig(config_selectors={'schema:stg', 'materialized:view', 'tags:tag_4', 'tags:tag_3', 'tags:yet_another_test_tag', 'tags:tag_1'}, upstream_models={'stg_payments', 'stg_orders'}))

...as opposed to this:

DbtModel(name='orders', path='dbt/jaffle_shop/models/orders.sql', config=DbtModelConfig(tags={'tag_4', 'tag_3'}, upstream_models={'stg_payments', 'stg_orders'}))

which will really simplify the process for a customer when it comes to using select/exclude because this is similar to how dbt does it (see here):

    jaffle_shop = DbtTaskGroup(
        dbt_project_name="jaffle_shop",
        conn_id="snowflake_chronek",
        dbt_args={"dbt_executable_path": "/usr/local/airflow/dbt_venv/bin/dbt"},
        test_behavior='after_all',
        select={ #this could also be an exclude parameter with the same value for the opposite effect
          "configs": ['schema:stg']
        },
        dag=dag,
    )

...additionally, it will be easier for our parser to do a single intersection instead of multiple for various selector types. LMK if you have any questions