Added embeddings to preprocess sql completions so that we downselect to an appropriate prompt size. This also gives us substantial performance improvements for model and table matching inference.

This reverts commit 90aa81de.

This reverts commit 8c853374.

It was causing issues with query validation when it appeared in
unexpected places (like as the options on an `[:aggregation 0]`
reference.)

The core logic is still from the release script in bin/release.
The change here mostly wiring it up to GitHub Action so that it can be trigged
upon a new git tag (during the release process).

* Increase the request timeout for Percy model editor spec

* Update e2e/test/visual/models/editor.cy.spec.js

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

---------

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

* MLv2: validate references inside queries

* Validate references

* Skip join-alias validation if we have a Card source query

* Test fixes 



* Use `metabase.mbql.util.match` for match stuff

---------

Co-authored-by: Case Nelson <case@metabase.com>

* initial changes

* add tests

* remove namespaces

* Update test/metabase/api/user_test.clj

Co-authored-by: Noah Moss <32746338+noahmoss@users.noreply.github.com>

---------

Co-authored-by: Noah Moss <32746338+noahmoss@users.noreply.github.com>

Resolves #29687

* Move `BreakoutStep` to its own directory

* Rearrange props

* Add unit tests

Models based on native queries were not producing any SELECT clauses previously. This fixes that and puts both native and mbql query aliases under test. Additionally, I'm reducing the enum count threshold for pseudo-ddls to 10. This seems low, but models on stats are quite large so we need a lower number. In upcoming work we should make this value adaptive.

Fixes #30108.

* [MLv2] Clean query to remove any parts that fail schema validation

* Fix metric query generation

* Make test parallel

* Fix joins schema

When the FE is rendering implicitly joinable columns, it doesn't use the
target table name. Instead it uses the name of the FK field on the main
table. This is useful because there might be multiple FKs to the same
table with different meanings (eg. both `supplier_id` and `customer_id`
point to `PEOPLE`). In this example the `:fk_reference_name`s for the
column groups would be `Supplier` and `Customer`.

Fixes #30109

Many settings are inappropriate for transfer between instances, so exported settings are limited to a subset of settings
related to appearance and UI behavior of the instance.

Co-authored-by: Emmad Usmani <emmadusmani@berkeley.edu>

* Add repro test

* Fix limit was not properly set for preview queries

This reverts commit 9ebf7eec.

There are now four families of FE builds:

- `build` does a one-shot dev build.
- `build-watch` watches for changes and does dev rebuilds; no server.
- `build-hot` is `build-watch` plus a development web server.
- `build-release` is a one-shot release mode build.

Each family has `:cljs` and `:js` variants, to build just one part.