In a working meeting, some prompt adjustments were tried. This change felt like the best incremental improvement,
considering feedback from users on stats.

We attempted to guide the LLM to return descriptions that:

 - don't state the chart type as if its *very* important (we can see what it is already, so its not that important)
 - do call out caveats and important specifics as implied by the question's filters, aggregations, and breakouts
 - are descriptive but not verbose
 - try not to state caveats too strongly

* Rename :model/Metric to :model/LegacyMetric
* Rename ::lib.schema.metadata/metric tp ::lib.schema.metadata/legacy-metric
* Rename models.metric/Metric to models.metric/LegacyMetric
* Move /api/metric endpoints to /api/legacy-metric

* SettingsSetting FC, change to named export

* adding unit test

* Rename api to just `dataset`

We're going to use this api for both structured and native endpoints.

* Fix the input type

* moving new item modals to be global

* adjusting unit tests

* Use Mantine Flex for the NotebookContainer

* Rename the component to `NotebookContainer`

* Convert to TS

* Explain the delay

* Use regular div

* Destructure the import type

* Simplify styling

* Shorten the prop name to `isOpen`

* v2 of minimal embed homepage

* useState instead of useMemo, fix unit tests

* address pr feedback

* use rtk for auditInfo

* destructured hook export

* fix rebase

* remove unused services definition

* handle double escape in entityPicker

* escape key test

* use fancy hook

* do not pass null values to link url

* update null check to include query builder nulls replaced with "(empty")

* add test to verify behavior

* replace magic string with constant

* fix breakout in cypress spec

This issue was previously punted, because the schema for aggregation
clauses allowed the tag to be `:any`. Now it's a short list of permitted
arithmetic expressions, but that list is too short and excludes things
like `:round`.

This change searches for an aggregation clause transitively in the
expression, and so allows any arithmetic expression.

* Add try-catch in Dimension.field()

* Fix the bug

* Fix the bug

* Fix the bug

* Move search-related snowplow tests to a separate file

* Update test names

* Move filters-related search tests to a separate file

* Extract search helpers into a separate file

* Revert test rename

* use rtk query for billing info

* capture more frontend errors

* improve fallback error experience

* Extract question function helpers

* Move question helpers

* Remove cy.archiveQuestion

* Replace cy.createQuestion usages in TS files

* Format code in JSDocs

* Fix comment

* Try removing Visualization hack for composeQuestion

* Try to remove composeQuestion

* Try to remove composeQuestion

* Try to remove composeQuestion

* Try to remove composeQuestion

* Try to remove composeQuestion