Make SemanticManifestLookup available for spec pattern creation

[tlento]

MetricFlow's query input parameter processing runs through a
pattern matching/parsing step that then produces a parameter spec
for subsequent matching during group by resolution. In practice,
every query parameter either directly references or is derived
directly from one or more elements in a semantic manifest.

Converting a parameter into a corresponsing spec pattern for a
given query input can, therefore, benefit from access to
the semantic manifest lookup objects we provide. This will
allow us to do things like map custom granularities to their
corresponding base granularities when doing group by resolution.

This change simply makes the semantic manifest available to the
method that converts between the query input parameter and the
spec pattern. It isolates the availability of the semantic
manifest lookup to this method because the other methods in the
relevant classes should generally not be using the lookup to
perform their operations, and the change as implemented
here also has a more limited blast radius.

[tlento]

• Switch query parameter classes onto ExpandedTimeGranularity #1404
• Make SemanticManifestLookup available for spec pattern creation #1403 👈
• Remove unused parse_object_builder_naming_scheme helper function #1402
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tlento and the rest of your teammates on Graphite

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[tlento]

Merge activity

• Sep 18, 11:48 AM PDT: @tlento started a stack merge that includes this pull request via Graphite.
• Sep 18, 11:50 AM PDT: Graphite rebased this pull request as part of a merge.
• Sep 18, 11:54 AM PDT: @tlento merged this pull request with Graphite.