* Install esbuild Cypress preprocessor

* Register esbuild preprocessor in Cypress plugins

* Remove Cypress webpack preprocessor

* Remove webpack references from comments

* basic logic for including params in dashboard subscriptions

* BE date formatting

* redo approach to date formatting locale

* refactor and use the same formatting code for parameters listed in subscription header

* fix tests and lint

* fix more tests

* fix final (?) test and fix namespace lint error

* a couple extra test cases

* fix tests

* new cypress test

* address braden and ngoc's comments

* fix tests

* guard against nil text in substitute_tags

* fixing tests and make chain-filter dashboard endpoints returns the flag

* remove using anonymous function in update

* Update dashboard endpoints and `FieldValuesWidget` to handle `has_more_values` scenario (#24022)

* update dashboard action/reducer

* Update FieldValuesWidget

* Update isSearchable to accept map of args

* Add unit tests for various FVW utils

* Split isSearchable logic a little

Co-authored-by: Dalton <daltojohnso@users.noreply.github.com>

* Simplify temporary DB path

* Set the port to 4000

* Move logic to create server config inside the base function

* Rename `kill` function to distinguish between it and Node process `kill`

* `createServer` as a method

* Remove reliance on Maps

* Stop server logic implemented directly in a method

* Remove unneeded parameter

* Start server logic implemented directly in a method

* Remove `isReady` from global scope

* Remove `delay` from the global scope

* Rename `BackendResource` to `CypressBackend`

* Rename file

* Simplify `CypressBackend`

No need to invoke the function when we can store everything
as method definitions under `CypressBackend` object.

* Pass `port` as an argument with default value

* Use template literals for logging

* Destructure `response`

* Fix small typo in the comment

* Tidy up `dbFile` in the `server`

This parameter makes the impression that Metabase can deal with encrypted
private keys, but this is not the case. The internal keystore password can just
as well be randomly generated in the code.

* Fix changing locale doesn't reload page

* Fix SSO users can't set language

* Address Alexander's feedback

* Fix rendering segment and metric revision history

* Address Alexander's feedback

* Remove unused styled-system props

* Remove `u/key-by`

* Fix typo

* SORT THE NAMESPACES

* Fix CircleCI job skipping magic: `$CIRCLE_STAGE` has been renamed to `$CIRCLE_JOB`

* Bust cache if `$CIRCLE_JOB` is unset

* Print message if `$CIRCLE_JOB` is unset and we're busting the cache

* Fix GoogleAnalytics status code

* adjust font size on scalar cards

* fix specs

To persist we need:
- a schema
- to be able to create, read, and delete tables in that schema.

So we run the following sql:

```sql
create schema "metabase_cache_134ba_45"
create table "metabase_cache_134ba_45"."persistence_check_8667" as values (1)
select * from metabase_cache_134ba_45.persistence_check_8667
drop table if exists "metabase_cache_134ba_45"."persistence_check_8667"
```

The `create table ... as values (1)` seems to only be valid in pg not redshift.

```sql
dev=# create table "metabase_cache_4b4bb_2"."persistence_check_9755" as values (1);
ERROR:  syntax error at or near "values"
LINE 1: ...tabase_cache_4b4bb_2"."persistence_check_9755" as values (1)...
                                                             ^
dev=# create table "metabase_cache_4b4bb_2"."persistence_check_9755" as select 1;
SELECT
dev=# select * from metabase_cache_4b4bb_2.persistence_check_9755 ;
 ?column?
----------
        1
(1 row)
```

But it is valid to use `create table ... as select 1`

This is also valid in pg so we are gold again.

* Update scanning process details

Product doc:
https://www.notion.so/metabase/Overhaul-field-values-scan-query-and-filter-widget-behavior-edc24a6ac4b54093ac1c5133345dcb3c#ab7c3aa6b5ce4d0aa39ef8edca1d0bdf

Relevant PRs:
https://github.com/metabase/metabase/pull/23138
https://github.com/metabase/metabase/pull/23403



* we trigger only one query

* revision

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

Co-authored-by: gitstart <gitstart@users.noreply.github.com>
Co-authored-by: GitStart-Chalktalk <nitesh.singh@gitstart.dev>
Co-authored-by: Gh0sT <coolmagnas@gmail.com>
Co-authored-by: Rubens Rafael <70234898+RubensRafael@users.noreply.github.com>
Co-authored-by: Benjamin Mayanja <vibenjamin6@gmail.com>
Co-authored-by: Júlio Piubello da Silva Cabral <julio.piubello@gitstart.dev>

* allow field values widget to fill width

* banish horizontal fieldvaluespicker scroll

* Define all Java flags separately for readability

* Separate database and snowplow configs

* Explicitly say that we are generating a temporary DB file

* Extract `userDefaults` and warn about it

* Rename `databaseConfig` to `metabaseConfig`

* Rename temporary database path generator

* Remove unused and non-existent ENV

* Export only resources actually used elsewhere

* Remove the default callback implementation

* Remove unused Cypress app db fixture

* Remove `DEFAULT_DB_KEY`

We're never ever going to use `test_db_fixture.db` to spin a Cypress instance up.
That was the only reason why `DEFAULT_DB_KEY` existed in the first place.

In order to fall back to using that fixture app db `dbKey` would have to be `undefined` or `null`.

* Simplify `get` method

Get the `dbKey` inline, rather than having to pass another callback
with the separate logic.

* Remove obsolete filter flag (see #19378)

* Remove unused Java flag

* Bring back `MB_USER_DEFAULTS`

This reverts 70ea7bedddb5cc1e221cff934c7c939e96bb43c8

* Link the PR that explains the origin of `MB_USER_DEFAULTS`

* disable erroring json filters
* better summarize action handling

Co-authored-by: gitstart <gitstart@users.noreply.github.com>
Co-authored-by: gitstart <gitstart@gitstart.com>
Co-authored-by: Benjamin Mayanja <vibenjamin6@gmail.com>
Co-authored-by: GitStart-Chalktalk <nitesh.singh@gitstart.dev>
Co-authored-by: Júlio Piubello da Silva Cabral <julio.piubello@gitstart.dev>

* Closing all Dashboard sidebars when entering/exiting edit mode

* fixing unit test

As the user in https://github.com/metabase/metabase/pull/14585#discussion_r922696696 quickly noticed, the key value syntax in Dockerfiles is legacy and also we shouldn't use it with more than 1 key. This didn't make any effect as the base image had our Env keys already there, but if there's a change at some point, we might end up with weird env settings

Cam suggested most of these changes in another PR, and I'm tackling them
here.

Fixes #23938

metabase.driver.ddl.postgres should be named metabase.driver.postgres.ddl
metabase.driver.ddl.mysql    should be named metabase.driver.mysql.ddl
metabase.driver.ddl.sql      should be named metabase.driver.sql.ddl

Renamed aliases to match new structure

* allow operator changes on category fields