[Feature] an option to add freshness: null for tables with filter

[mhanninen]

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

hello,
I would like to ask if its possible or to suggest an extension of functionality to be able to disable source freshness check based on filter boolean statement.
Currently the way it works is:
if i add freshness: null for a specific table in sources.yml and a filter, it will skip the freshness check no matter if filter returns true or false.
if i add the actual values for warn_after or error_after and a filter, the result of dbt source freshness is being filtered returning WARN/ERROR or PASS depending on the values for count.

Please let me know if i missed anything and its possible to skip freshness check based on filter.
Thanks,
Mariia

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response