Remove unsupported legacy MetricFlow Client API

[tlento]

In the original version of MetricFlow we supported a Python
client for programmatically issuing queries. This was a thin
wrapper over our internal APIs for running queries against
SQL engines.

Since the acquisition of Transform by dbt Labs the direction of
MetricFlow has shifted heavily (and appropriately) in the direction
of being a support library for building and rendering metric queries
against target query dialects (currently all SQL).

This legacy public API has not been maintained at all - it uses legacy
string-typed inputs, it does not support saved queries, and it allows
for a highly limited scope set of operations.

Furthermore, it is in a package directory path that indicates we have
a public API. Since we do not, in fact, have a supported public API
just yet, it behooves us to remove this in order to unblock some
efforts to simplify our internals and move us closer to the point
where we can build out a publicly supported API, whenever that time
may be.

[tlento]

• Update dbt-semantic-interfaces to 0.5.1 #1104
• Move MetricFlow CLI package to dbt-metricflow #1099
• Streamline MetricFlow build contents #1097
• Move metricflow/test package to repo root tests/ directory #1096
• Update Ruff to 0.3.3 #1095
• Remove unsupported legacy MetricFlow Client API #1094 👈
• 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.

[WilliamDee]