Release `v0.207.3` (#1711)

This is the release PR for `0.207.3`. To avoid an unresponsive UI, the
actual set of commits can be see in branch
`p__release_0.207.3_updates__01` and includes the following:

```
 32: e0da921 Update `metricflow` `0.207.3.dev0` / `dbt-metricflow` to `0.8.2.dev0`.
 31: d4b32fe Allow querying SCDs without `metric_time` (#1621)
 30: 85c3a5e Fix off-by-one issue in pretty-formatter (#1665)
 29: 3a0b5e1 Update handling for Pydantic objects in `mf_pformat` (#1666)
 28: e991c5e Allow for a one-line representation in `mf_pformat_dict()` (#1667)
 27: c5d7f8f Allow for lazy-evaluation of arguments in `LazyFormat` (#1669)
 26: a18cc65 Remove unused class (#1674)
 25: 04106d1 Fix `JoinToTimeSpineNode.with_new_parents()` (#1672)
 24: 2a3f25f Add `--quiet` option to the `query` CLI command (#1680)
 23: 0044633 Upgrade Jinja to fix a security vulnerability (#1684)
 22: 267ea22 Add `duckdb_only` marker to CLI tests (#1689)
 21: 6a0e039 Use snapshots for CLI tests (#1690)
 20: a9b75ff Update tutorial project to use `ref()` (#1691)
 19: f87d0ab Specify DB file path in tutorial-project profile (#1692)
 18: 2544398 Allow `CliConfiguration` to be loaded from specified paths (#1693)
 17: a03b8ba Remove `dbt` project metadata dependency in tutorial project generation (#1694)
 16: c26e58c Avoid reinitialization of `CLIConfiguration` (#1697)
 15: a3c1db9 Add process-isolated CLI runner for tests (#1695)
 14: be56e43 Migrate CLI tests to use the process-isolated CLI runner (#1696)
 13: b87d770 Add test case to capture display of various data types for `mf query` (#1698)
 12: cf26759 Address issues with the display of numeric types (#1699)
 11: 47598f9 Address display of `None` in the output of `mf query` (#1700)
 10: 5a23e98 Address display of whitespace-padded strings in the output of `mf query` (#1701)
  9: 781ce07 Add support for `DBT_PROFILES_DIR` / `DBT_PROJECT_DIR` in the CLI (#1702)
  8: 3336aeb Update snapshots to reflect older `dbt-core` version.
  7: 729c6b6 Add artifact modified time to CLI error messages (#1708)
  6: 8c62e73 Use native Python methods to manage the CSV file handle (#1709)
  5: 5cffe24 Configure `pytest` to skip scanning snapshots directory (#1710)
  4: 1f155cd Backport updated error message for missing time spine (#1707)
```

Release `0.207.2` (#1661)

The `0.207.2` release adds a number of commits from `main` that were
previously excluded in `0.207.1` due to the breaking
`dbt-semantic-interfaces` version change. The goal was to include many
commits so that more fixes are included, and so that future backports
would be easier to do. The backported commits can be viewed by comparing the [p--release-0.207.2-updates--01](https://github.com/dbt-labs/metricflow/tree/p--release-0.207.2-updates--01)
branch and the
[release-0.027.2](https://github.com/dbt-labs/metricflow/tree/release-0.207.2)
branch. I left those cherry-picks in a branch since the PR would not
load reasonably.

More commits could be included, but there are more complex conflicts to
resolve.

Update `hatchling` to `1.27.0` (#1639)

Updating the version of `hatchling` resolves an issue in the workflow to
publish the package to Pypi:

```
ERROR    InvalidDistribution: Invalid distribution metadata: license-expression 
         introduced in metadata version 2.4, not 2.1     
```

Release PR for MetricFlow 0.207.0 (#1600)

Update attribution, version, and changelog for 0.207.0

Update dbt-metricflow version to 0.7.1 (#1363)

This update will be deployed as a patch release on the 0.7.0 minor
version.

This was tested by building locally and installing the build
to run a sequence of CLI commands.

Upgrade DSI & bump dev version

Update package version to `0.207.0.dev1` (#1297)

As per title

Update package version to `0.207.0.dev0` (#1289)

As per title.

Release PR for MetricFlow 0.206.0 (#1260)

Update attribution, version, and changelog for 0.206.0

Update dbt-metricflow version to 0.7.0 (#1261)

With the release of MetricFlow 0.206.0 we can update dbt-metricflow
to reflect that dependency change and deploy the new version.

Note our build reshuffling incidentally renamed the extras to full
package names, so `pip install dbt-metricflow[postgres]` must now be
`pip install dbt-metricflow[dbt-postgres]`, which, while more typing,
does seem like an improvement since it's more obvious which package
the extra command actually installs.

To test the build, I ran the following from repo root:

```
$ cd dbt-metricflow
$ hatch build
```

From there, I created a clean venv and ran variations on pip install
commands from the local builds and fired up the MetricFlow CLI. For
example:

```
$ python -m pip install "$HOME/sources/metricflow/dbt-metricflow/dist/dbt_metricflow-0.7.0-py3-none-any.whl[dbt-postgres]"
...
$ mf --version
mf, version 0.7.0
$ mf query --metrics order_cost --group-by metric_time --order metric_time --where "{{ TimeDimension('metric_time', 'day') }} > '2017-01-01'" --limit 5
✔ Success - query completed after 0.31 seconds
metric_time__day       order_cost
-------------------  ------------
2017-01-02T00:00:00        285.24
2017-01-03T00:00:00        328.94
2017-01-04T00:00:00        294.73
2017-01-05T00:00:00        340.78
2017-01-06T00:00:00        329.86
```