* Updating to cypress 12

* updating deps

* Updating Tests. Be Green Plz

* removing custom test id from select button

* Select Button Tuning

Co-authored-by: Nick Fitzpatrick <nick@metabase.com>

Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>

Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>

* WIP action data type tests

* DRY up the actions tests

* lots of type tests

* make the tests work

* reorganize tests

* WIP action data type tests

* DRY up the actions tests

* lots of type tests

* make the tests work

* reorganize tests

* reduce some flakes

* better time formatting in action forms

* sort out all the timezones 



* update after rebase

* rebase disaster

Co-authored-by: Ryan Laurie <30528226+iethree@users.noreply.github.com>

* Register new E2E path alias

* Move E2E support files

* Move E2E runner files

* Move E2E snapshot related files

* Move E2E visual regression tests

* Move E2E `downloads` scenarios

* Move E2E `admin` scenarios

* Move E2E `auditing` scenarios

* Move E2E `bining` scenarios

* Move E2E `ccollections` scenarios

* Move E2E `cross-version` scenarios

* Move E2E `custom-column` scenarios

* Move E2E `dashboard` scenarios

* Move E2E `dashboard-filters` scenarios

* Move E2E `dashboard` reproductions

* Move E2E `embedding` scenarios

* Move E2E `filters` scenarios

* Move E2E `joins` scenarios

* Move E2E `models` scenarios

* Move E2E `native-filters` scenarios

* Move E2E `native` scenarios

* Move E2E `onboarding` scenarios

* Move E2E `organization` scenarios

* Move E2E `permissions` scenarios

* Move E2E `question` scenarios

* Move E2E `visualizations` scenarios

* Move E2E `sharing` scenarios

* Move E2E `docker-compose`

* Fix commands imports

* Fix helpers imports

* Fix downloads reproductions imports

* Fix integration imports

* Move visual regression tests

* Various fixes

* Move `validate-e2e-files` script

* Add eslint rules for E2E folder

* Improve file paths

* Move `cross-version` tests into scenarios

* Path fixes

* Register E2E alias in tsconfig

* Fix failing tests after rebase

Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>

Co-authored-by: Ryan Laurie <30528226+iethree@users.noreply.github.com>

Dev experience:
- CLJS now has source maps
- Devtools extension renders CLJS data in Chrome (et al) Devtools
- Use a debug build of CLJS in the tests
- Fixed line numbers and breakpoints being off-by-one in Devtools

CLJC infra:
- More robust direct approach to JS<->CLJS conversions, powered by
  Malli transformers.
- Powerful `define-getters-and-setters` macro to generate the accessors.

* Expand the glob to include TS(X) files

* Use console error

* Re-order imports

* Print the missing files in red

* Fix glob pattern

* Add script to pre-commit hooks

* Remove the check from CI

* Upgrade `esbuild` to `0.17.9`

* Upgrade `@bahmutov/cypress-esbuild-preprocessor` to `2.2.0`

* Add script validating e2e test file names

* Move helper files to helper directories

* Fix whitespace before the first file name

* Add node shebang

Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>

* Check if staged files include relevant files from `scenarios` folder

* Distinguish between staged files and all files

* Add precommit hook

* Update binning folder structure

* Improve glob pattern

* Add back forgotten binning constants

* Update cross-version folder structure

* Update embedding folder structure

* Update embedding folder structure

* Update dashboard-filters folder structure

* Use all caps for global vars

* Address feedback: consistency

* Simplify functions

* Actually exit the process

* Adjust script for use with `lint-staged`

* Apply another suggestion to optimize script

* Improve naming of boolean checks

* Fix the init logic

---------

Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>

* Suppress console error on CopyWidget

* Remove old component lifecycle deprecation warning from a library

* Fix inconsistent modal transition

* Fix ESLint error

* qa db ergonomics improvments

* cleanup

* `nock` behave differently between v14 and v16+

* Remove xmlhttprequest

* [ci skip] Add a comment warning people to not upgrade CI node version

As it might break the unit tests.

This adds a cross-platform date/time formatting library in CLJC, with
(nearly) identical output in both JVM and JS environments.

The only known difference is week numbers.

CLJS (through Moment.js) has ordinal numbers, and renders the week
number as "34th". Neither the JVM nor Clojure has a handy library for
this (I'm sure it's out there somewhere, but it seems like a silly
dep to add) so it renders week numbers as simply "34".

Both platforms have date formatters that use pattern strings (eg.
`"YYYY-MM-dd"`) to turn date/time objects into strings. There's a strong
resemblance in how these work and what letters stand for what parts of
the date and time, but they are far from identical.

Rather than try to hackily convert one set of strings to another with
regexes or other manipulations, this PR defines a set of names for
fragments of dates (eg. `:year`, `:day-of-week-full`, `:hour-24-dd`)
and includes functions to transform a list of these keys into a
platform-specific format function.

This is portable and transparent, and can be written in Clojure or
JS code:

```clj
[:year "-" :month-dd "-" :day-of-month-dd]   ; 2022-04-08
[:month-full " " :day-of-month-d ", " :year] ; April 8, 2022
[:hour-12-dd ":" :minute-dd " " :am-pm]      ; 7:52 AM
```

```js
[":year", "-", ":month-dd", "-", ":day-of-month-dd"]   ; 2022-04-08
[":month-full", " ", ":day-of-month-d", ", ", ":year"] ; April 8, 2022
[":hour-12-dd", ":", ":minute-dd", " ", ":am-pm"]      ; 7:52 AM
```

Note that the original code allowed an unrecognized `:date-style` string
to be used directly as the formatting string. With the move to
formatting data structures that no longer works. Instead there is a
fixed map of format strings to the above data structures, that contains
all the currently used `:date-style` inputs.

If some caller needs a new format someday, we can either: (a) add the
style to the map; or (b) pass the data structure form directly to the
`:date-format` option, which if provided is used as the format.

It's tempting to go to all the call sites and replace these `:date-style`
strings with the new format structures. However, the strings are still
embedded in the `:visualization_settings` in user appDBs, so we still
need to recognize them.

Most of the existing functions in the TS library have the same API.

The set of allowed `:date-style` and `:time-style` values is turned into
a type using `keyof`, so that we get precise type-checking of these
values rather than simply `string`.

One function has been dropped from the API: `getDateFormatFromStyle`.
There was no practical way to implement it using the new format data
structures. The only caller was the date format column settings, and it
has been rewritten to use the formatted string for its sample date as
its key instead.

* Removed forced `node-forge` resolution

It now resolves to the `version "1.3.0"` anyway.

* Removed forced `nanoid` resolution

It now resolves to the `version "3.1.31"` anyway.

* Removed forced `immer` resolution

It doesn't appear in the list of dependencies anymore.

* Removed forced `prismjs` resolution

It doesn't appear in the list of dependencies anymore.

* Removed forced `minimist` resolution

It now resolves to the `version "1.2.6"` anyway.

* Removed forced `nth-check` resolution

It now resolves to the `version "1.0.2"` anyway.

* Install and enable plugins

* Run eslint auto fix

* Fix linter issues (part 1)

* Fix Visualization test

* Fix Pie Visualization test

* Add `getIcon` and `queryIcon` helpers

* Fix `VisibilityToggler` tests

* Fix `QuestionActivityTimeline` tests

* Fix formatting tests

* Fix `EntityMenuItem` tests

* Fix `ClampedText` tests

* Fix `ObjectRelationships` tests

* Fix `EmailAttachmentPicker` tests

* Fix `SavedQuestionHeaderButton` tests

* Fix `DatabaseEngineWarning` tests

* Fix `Tooltip` tests

* Fix `TippyPopoverWithTrigger` tests

* Fix `TippyPopover` tests

* Fix `TableLabel` tests

* Fix `TableInfo` tests

* Fix `ModerationStatusIcon` tests

* Fix `Sidebar` tests

* Fix `PermissionSelect` tests

* Fix `PinnedItemCard` tests

* Fix widget tests

* Fix `DimensionSemanticTypeLabel` tests

* Fix `ListSearchField` tests

* Fix `ControlledPopoverWithTrigger` tests

* Fix `FieldFingerprintInfo` tests

* Fix `ErrorActionButton` tests

* Fix `QueryValidationError` tests

* Fix `LineAreaBarRenderer` tests

* Fix `DataSelector` tests

* Fix `PivotTable` tests

* Fix `ItemPicker` tests

* Fix `TokenField` tests

* Fix `TagEditorParam` tests

* Fix tests

* Fix tests

* Run prettier

* Fix tests

* Install `eslint-plugin-jest`

* Enable `eslint-plugin-jest`

* Run eslint auto fix

* Fix linter issues

* Fix get-column-key

* Fix extra space

* Fix ChartSettingFieldPicker

* Fix eslint issues

* Remove redundant describe

We were 4 major versions behind.
There were a lot of breaking changes, but none that affect how we use this library.

* check how much is broken after redux upgrade

* fix popovers could not use connected components

* fix a unit spec failure

* fix accessing a connected component ref which is a class instance

* supress typescript errors caused by better type inference of the newer react-redux