* Don't update tables in a schema one by one

Code had wanted to log each table which is admirable. But on bigquery
there can be 15,000 tables and this will lock up calls to
/api/database. On stats they are taking about 18s for me. Need to do
once and let the db do the heavy lifting

* Also where schema is nil

* slightly better query

When the text representation gets reformatted, the old caret position
might not be sensible anymore. Hence, just push the caret to the end.

* Add e2e test for caret position after blur and refocus

Co-authored-by: Gustavo Saiani <gustavo@poe.ma>

* Add Pulse URL param to email settings

* Undo frontend changes -- make config only allowable by env var

* Make config enterprise only

* Address feedback

* Change namespace and token feature

* newline

* Rename var and add docs

* Cache dashboard parameter values

* move some logic to utils files

* Fix e2e tests

* add comment + const to clarify getParameterValuesSearchKey

Add functions to describe-database namespace for performing inclusive/exclusive schema filtering

Add tests for these functions in isolation

Update `:bigquery-cloud-sdk` driver and QP code to remove the single `dataset-id` conn-param

Changing :bigquery-cloud-sdk` driver to use dataset inclusion/exclusion filters instead

Updating `add.cy.spec.js` Cypress test to account for new structure

Add data upgrade (via `driver/normalize-db-details` implementation) to change `dataset-id` property to inclusion filter

Add test to confirm data upgrade

Adding server side expansion of `:schema-filters` type connection property

* Misc code cleanup

* PR feedback

* pratt parser diagnostics

* ported over tests from custom parser branch

* updated error types to support pos/len for error markers

* updated compiler error to removed unnecessary plural

* updated resolver to use new error type and pass through node information

* updated error text in custom column e2e test

* updated diagnostics to use new resolver error class

* update recursive-parser passes to pass through node information

* roll back error text fix in e2e tests

* deleted fuzzing tests (they will be moved into the metabase/expression repo)

* this is weird, setting e2e error text back to "Expected expression"

* rolled back expression editor changes in handleInputBlur and moved diagnoseExpression first to fix exponent rewrite issue

* roll back changes to compileExpression

* update import paths in expressions case class identities get messed up

* Debugging QP Improvements

* Appease namespace linter

* Backport additional debug QP changes from #19384

* Test fix 

* Fix creating a new collection from navbar

* add specs

Repro #19494: Dashboard filter with default value sends the wrong parameters to all cards of the same questions

* Build and publish branches

* fixup whitespace

* Update docker.yml

Co-authored-by: Kyle Doherty <5248953+kdoh@users.noreply.github.com>

* update nav copy to be clearer

* update tests

* Exclude archived collections from tree view

This is a bit more nuanced that it might first appear. The bug report is
the permissions editor for collections is showing child collections
which are archived. But the api sends back ALL collections, regardless
of archival state. So the FE knows to omit top-level archived
collections but not archived child collections.

So we thought about just having the FE remove all archived ones, but
best to remove it from the response. One worry is that we're not sure if
any callers want archived collections in the tree view or not. So right
now they are removed with a `?exclude-archived=true` query param, but if
we can demonstrate that no callers of the tree api ever want archived
items we can make this the behavior, rather than an optional behavior.

To verify that the tree api is sending back all collections, you can
check

```clj
collection=> (collection/collections->tree
               {}
               [{:archived false
                 :name "foo"
                 :id 1
                 :location "/"}
                {:archived true
                 :name "foo"
                 :id 2
                 :location "/1/"}
                {:archived true
                 :name "its archived"
                 :location "/"
                 :id 3}])
;; we have always sent back archived collections, both top level and children
({:archived false,
  :name "foo",
  :id 1,
  :location "/",
  :children ({:archived true,
              :name "foo",
              :id 2,
              :location "/1/",
              :children ()})}
 {:archived true,
  :name "its archived",
  :location "/",
  :id 3,
  :children ()})
```

* hide archived collections from the collections permissions page (#19616)

* fix incorrect issue number

Co-authored-by: Alexander Lesnenko <alxnddr@users.noreply.github.com>
Co-authored-by: Aleksandr Lesnenko <alxnddr@gmail.com>

* Hide table popover based on a few conditions

* fix TS id type inference

* use util fn

Pursuant to the nits from #18678 and #18676

This actually has nothing to do with waterfalls. Really, it's that static viz is brutally incompatible with bignum types, bigint and bigdec. However, nothing will fit in the screen anyways if you actually need a bignum or bigint type so the solution was to just coerce and be OK with exploding if it actually needed bignum range.

* add delay prop to table/dimension info popovers

* move isCypressActive delay check to TippyPopover

Seems that the very first focus happens when the element ref isn't ready
yet (the component did not completely get mounted).

* simplify nav options [ci skip]

* icon tweaks [ci skip]

* dismiss when clicking items [ci skip]

* lint

* Prototype/create button (#19587)

* fix create menu not closing

* update specs

* lint

* fix more specs

* fix specs

* specs

* clean up

* specs

Co-authored-by: Alexander Lesnenko <alxnddr@users.noreply.github.com>
Co-authored-by: Aleksandr Lesnenko <alxnddr@gmail.com>

* don't try to show number fingerprint for ID fields

* add repro

* Allow override of WEEK_START in Snowflake driver

Incorporate the following sources of WEEK_START, in decreasing order of precedence:
1) the connection string, a.k.a. additional-options (ex: WEEK_START=N)
2) the Metabase "start-of-week" setting (i.e. day of a week)
3) the default value (7: Sunday)

Adding new fn to the driver.common namespace to parse a connection string param out of additional-settings (plus a test for that)

Adding Snowflake driver test to ensure that all cases above are covered as expected, by invoking the DAYOFWEEK function on a set of fixed dates

Update documentation for start-of-week setting to clarify that it now influences this behavior

Swap out parse-additional-options-value for additional-options->map instead (more generic)

Update test accordingly

* downgrade cypress to 6.4

* add resolution to cypress 6.4.0