[Feature] Allow metric and input metric/measure filter elements to be lists as well as strings

[tlento]

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 change to existing dbt-semantic-interfaces functionality, rather than a Big Idea better suited to a discussion

Describe the feature

We are planning to push down predicates wherever possible, and we want to provide users with the ability to hint that predicates can be safely pushed down. The mechanism we've chosen is to allow users to specify a list of filters, where the final results will effectively apply ALL of the filter statements in the list. In this way, users can hint to us that given predicate can be pushed down by simply placing it in its own list element. See dbt-labs/metricflow#747 for details.

In order to support this for filters provided in the config (in addition to filters passed in to the where selector at query time) we need the config schema to accept either a List[str] or str type as it does today.

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