[Feature] Add cache config to saved query

[Jstein77]

Is this your first time submitting a feature request?

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

Describe the feature

To enable declarative caching you need to be able to specify if a saved query should be used to populate the cache. Users can set cache: enabled: true | enabled as a configuration of a saved query. The saved query spec is below:

saved_queries:
    - name: my_query
        description:
        query_params:
            ...
        exports:
            ...
                config:
                  cache:
                    enabled: true|false

Describe alternatives you've considered

No response

Who will this benefit?

Users who want to increase the performance of saved queries.

Are you interested in contributing this feature?

No response

Anything else?

No response

[graciegoheen]

@Jstein77 I know we talked about this awhile back, can you remind me the reason we went with adding this as to the config: so it's captured here. I believe it was for parity with the way enabled works for other resource types in core (docs here). Were we also imagining someone might enable the cache for a set of saved queries?

[Jstein77]

@graciegoheen that's correct!

[emmyoop]

cache is now supported in dbt-core with https://github.com/dbt-labs/dbt-core/pull/9588.