* SQL Lineage: Create the QueryField model

This links Cards (with native queries) to Fields, showing us which
queries use which Fields.

QueryFields are automatically maintained as part of the Card lifecycle

Cards with stale queries (powered by QueryField info) are exposed via the `card?f=stale` API

Fixes a problem introduced in #39782

Co-authored-by: Chris Truter <crisptrutski@users.noreply.github.com>

* explicit callout for data download

* rephrase "data download" -> "download results"

* review suggestions

* wrong link

* updated pot file for v49

* update translations for 49

* Upgrade Cypress grep library to its latest version

* Add Cypress grep types to our E2E TS config

* PoC: Convert existing JS Cypress spec to TS

* some clarifications around subscriptions

* Apply suggestions from code review

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

---------

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

Correctly show a selected table (in the data selector) which comes from a multi-schema database (#39930)

* Show selected table in the data selector

Fixes #39807.

* Build schema information when table is selected

* Remove now unused method

* Update only the selected schema id information

* Obtain schema id from the state

* Introduce multiple schemas to the writable database

* Add E2E reproduction for #39807

* Fix unit test

* Fetch schema if needed according to the new condition

Co-authored-by: Tim Macdonald <tim@metabase.com>

This reverts commit 9413706b.

* Add reproduction for spaces breaking the search in filter pickers

* Search using display name too

* Search using display name in summarize picker

* v1

* v1

* v1

* Move sync code

* Small refactor

Repro #29943 - Wrong field highlighted when editing model metadata if custom column added to left of column (#39996)

* Repro #29943 - Wrong field highlighted when editing model metadata if custom column added to left of column

* Refactor assertions

* Reuse getHeaderCell

This matches how models are visualized, and how the parameters are
attached to them in the first place - an extra ad-hoc query is wrapped
around the model.

Because of that wrapping, a parameter will be targeting a model's field
by name rather than by ID, but that parameter cannot be applied directly
on the model's last stage.

Fixes #39940.

* move log-enabled? into premium-features

* only `record-views!` when `log-enabled?`

* test that view-log entries arent created in oss

* simplify test

* fix new test fails: we don't log views in OSS.

* fix 3 more view logging tests (they dont do anything in oss)

* fix dashboard-read-ee-test

- check for `log-enabled?` not `ee-available?`

* fix the rest of the tests

- Only check for view logs when (premium-features/log-enabled?) is falsey

* adjusting e2e test

---------

Co-authored-by: Nick Fitzpatrick <nickfitz.582@gmail.com>

* Add issue number to todos in models.card

* Add issue number to todos in models.pulse

* Add issue number to todos in models.dashboard-card

Fixes #39657.