hook check-model-has-meta-keys not correctly identifying defined meta key

[fredmny]

Describe the bug
We are using the check-model-has-meta-keys hook to check if our models have owners defined, but even with the key correctly defined (I also checked manifest.json to be sure) the hook raises an error for the models saying the owner is not defined.

It seems it's not seeing the meta keys defined at a folder level, since we are defining in our dbt_project.yml

from manifest.json:

        "model.analytics.analytics_ci_runs": {
            "raw_sql": "...",
            "compiled": true,
           ...
            "config": {
                "enabled": true,
                "alias": "ci_runs",
                "schema": "...",
                "database": null,
                "tags": [
                    "daily"
                ],
                "meta": {
                    "is_gold": true,
                    "owner": "analyt....@.....t.com.br"
                },

And the response from the hook:

If this is actually an error I'd be glad to contribute if you could point me in the right direction

To Reproduce
Steps to reproduce the behavior:

1. Add owner to group of models (folder) in dbt_project.yml file
2. Add following config to the .pre-commit-config.yaml

      - id: check-source-has-meta-keys
        args: ['--meta-keys', 'owner', "--"]

4. Execute pre-commit

Expected behavior
A clear and concise description of what you expected to happen.

Version:
v.1.0.1 of dbt-gloss

Additional context

[vsayer]

It'd be great to have support for checking meta at the dbt_project.yml level!