[Bug] Inconsistency between time dimension Jinja objects for `time_granularity_name`

[courtneyholcomb]

Is this a new bug in dbt-semantic-interfaces?

• [X] I believe this is a new bug in dbt-semantic-interfaces
• [X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Currently, the protocol for QueryInterfaceTimeDimensionFactory requires time_granularity_name to be set. This is inconsistent with other interfaces, where granularity is not required and can be resolved at query time.

Expected Behavior

I should be able to use a time dimension like {{ TimeDimension('metric_time') }} in all interfaces & parameters without error.

Steps To Reproduce

Try running a saved query that uses a group by parameter like: {{ TimeDimension('metric_time') }} You should see an error.

Relevant log output

No response

Environment

- OS:
- Python:
- dbt:
- dbt-semantic-interfaces:

Additional Context

No response