Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Today, our ConfigSelectorMethod supports selection from parsed and source nodes only.

As an example, you can do this dbt ls -s config.meta.contains_pii:true, but this command won't return any saved queries that have this meta key in the config, despite us using configs for other purposes (as documented).

Describe alternatives you've considered

No response

Who will this benefit?

From a customer directly:

Our main use case here is tying our business definitions back to actual saved queries/exports/metrics etc. We're hoping to leverage this with dbt Explorer to help our end users understand the full lineage for a given business metric definition (these can be a one-to-many relationship in terms of semantic models, measures, metrics, etc). I'm also hoping to eventually use it in our metric processing jobs, as some of the metadata parsing we're doing could be simplified if we were able to select saved queries and their parents using an inbuilt method vs manually parsing to find it.

Are you interested in contributing this feature?

Sure! I believe it should be a pretty straightforward extension but looking for guidance on whether or not that's the case before I get going.

Anything else?

No response