* fix invalid js

* install typings using typesync

* upgrade classnames to get its own typings

* convert colors, settings, Icon to TS

The possible matching/choices for function names, dimensions, segments,
and metrics are only shown when there is at least ONE matching character.
Thus, when the user hasn't inputted anything yet, there won't be any
suggestions.

* Repro #18630

* Ignore field literals in Join's isValid check

* Don't use Join's `isValid` method at `clean`

* Update the keys we consider to unverify a card

Previously when almost anything changed we would unverify a card. But
this was way too aggresive. We really only want to unverify when a query
changes. Far simpler to specify the keys we do want to consider rather
than the keys to ignore.

Was prompted because when we marked a question as a dataset it would
unverify because the `:display` was changed and also `:dataset`. Neither
of these matter for verification purposes

* Update testing context string [ci skip]

* Empty commit to trigger CI

had skipped ci since it was a docstring change but that prevents merging
sad face :(

`org.apache.sshd` requires `net.i2p.crypto/eddsa` dependency
to work with ED25519 keys.

This worked in 0.40 because `eddsa` was included as a transitive
dependency of another unrelated dependency (`buddy`) but stopped
working in 0.41 because the new version of `buddy` no longer depends
on `eddsa`. Thus, we must explicitly include the dependency.

To prevent this from breaking again, switched one of the test
keys to an ED25519 key.

* move dashboard parameter utils

* Move the ParameterSection type to type/Parameter.js

* Handle long running sync in connection pool hash check

Modify the logic in `db->pooled-connection-spec` to check for the latest `DatabaseInstance` from the app DB in case of a hash mismatch, before deciding that the pool needs to be invalidated (based on changing hash of db details)

This is to handle the case where a long running sync keeps passing in a stale version of the `DatabaseInstance` over a period of many minutes/hours, long after the app DB has received an updated version that was saved through the UI

In this case, the connection pool code will get the latest `DatabaseInstance` from the app DB, on a hash mismatch, then compare that against the in-memory has for the given DB ID.  And if it still doesn't match, then the invalidation kicks in

Updating the test accordingly

* Add dataset icon

* Add getter and setter for Question's `dataset` flag

* Add action to turn a saved question into a dataset

* Add UI for turning a question into a dataset

* Use dataset icon for questions turned into datasets

* Show datasets on collections page

* Change colors for dataset icons in collections

* Test can turn a question into a dataset

* Fix unit test

* Fix color literal

* Hide "Turn into a dataset" button for datasets

* Rerun non table question when turned into a dataset

* This was a mistake

* Make the checkins_interval transient datasets more uniquely named

Append a timestamp suffix (initialized when the namespace was loaded) to transient dataset names

Add verbose comments explaining what we're doing

Add transient-dataset? functions for both BQ drivers to put logic in one place (which currently just see if the dataset is named `checkins_interval_*`

Ditch the "legacydriver_" prefix from the legacy BigQuery driver when creating new datasets; it's no longer needed now that transient datasets will have a much more unique suffix

Update the logic for the transient dataset suffix so that it can be more easily detected/parsed later (for cleanup)

Remove old (more than 2 hours) transient datasets when test extensions namespaces load

Add various docstrings

* move parameter ui utils to separate file

* move utils for building parameters from cards to own utils file (#18691)

.git is necessary so that some later steps (determining Uberjar version)
can work correctly.

Co-authored-by: Alexander Polyankin <alexander.polyankin@metabase.com>

* move parameter values logic to own utils file

* fix lint error resulting from rebase

#18646 Repro: Cannot select granularity/binning on fields from SQL question, which is joined (#18661)

* move target utils to own file

* move parameter to mbql functions to own utils file (#18663)

* Summarize sidebar improvements

* Summarize sidebar specs

* cursor pointer for add aggregation button

* review fixes

* move mapping options function into own utils file

* pull out option-building logic into own functions

This reverts commit c6688f5caf226c6ec5be424859fc00b93665620f.

Redshift only supports VACUUM command at a time on the whole
cluster, so running VACUUM can fail with parallel executions.

v2.0.0.3 -> v2.1.0.1

* Add dataset flag to Card

* Set dataset viz type to table

* Include datasets in collection children

* Ensure can write as dataset, include more tests

* add parameters/constants file for options-related constants

* add feature-flag utils file

* move dashboard parameter options logic to own utils file

* pull out mapping logic into own function

#18011 Repro: Post aggregation drill-through by dragging/selecting a portion of a chart results in an error (#18651)

* Add repro for #18011

* Expand the repro to include different granularity

Confirms that the issue doesn't work for "foo-of-bar" granularities.