Add time granularity handling configuration

[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

See dbt-labs/metricflow#714 for background context.

Sometimes users have a granularity set for a time dimension that is coarser than the granularity stored in their warehouse. While this does not follow our recommended practice, there are valid use cases for doing so. As such, we need to be able to coerce the data into the expected granularity when needed.

However, we do not want to just date_trunc() everything all the time, as that leads to confusing SQL and wasted processing.

The solution we've settled on is to provide a configuration parameter users can set to conform the values to the specified granularity.

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

[tlento]

Update - this is now a backlog enhancement that may never get built, as we've decided to always coerce to granularity. We will see if a need for this emerges in the near future, so let's hold this open for now.