* Switch to Toucan 2 part 1

* Fix Kondo errors

* Switch to Toucan 2, part 2

* Fix Kondo errors

* Bump clj-kondo to 2022.12.10

[Fixes #27512]

* Use Kondo's :config-in-call instead of grosser hacks

Ordering in nested queries doesn't have to affect how rows are returned
from the embedding queries.

* Switch to Toucan 2 part 1

* Fix Kondo errors

* add section to dashboard subscriptions on permissions

* feedback from Luiz

Use the vertica/vertica-ce:12.0.2-0 image.

* add PivotTable unit tests

* obey the linter

* measure leftHeader cell content

* test cell data width detection

* extract static properties

* convert to functional component

* cleanup refs

* extract cellRenderers

* extract size and position getter functions

* replace item measurement

* convert rowToggleIcon to typescript

* convert PivotTable to typescript

* remove unused hasCustomColors

* update tests to typescript

* fix rebase

* Update dashboard save to save all dashcard data on create, not update

* Remove repro e2e test

* Add e2e test

* Add series to POST request, missing by mistake

* Formatting

* Rename DashboardApi methods for consistent names and cases

* Add Fira Code

* Add basic actions tab

* Add "New action" flow

* Fix actions tab width

* Fix code doesn't show newlines

* Add action editing flow

* Fix console error

* Use Monaco for code snippet

* Add an empty state

* List implicit actions

* Make it possible to add implicit actions

* Hide actions tab if actions are turned off

* Handle read-only permissions

* Fix loader

* Sort actions

* Add server mocks for action endpoints

* Add `createMockImplicitCUDActions` helper

* Add tests for the actions tab

* Add E2E test for action create-read-update flows

* Clean up

* Move e2e test to models for now

* Fix `EmptyState` usage

* Fix action sorting

* Avoid boolean casting

* Ensure the page explicitly loads database

* Use existing color for action query card

* Use `space` function

* Fix length check

* adding onlyText button variant

* PR feedback

* Move `PublicApp` to its own directory

* Fix `renderWithProviders` for public environment

* Clean up `PublicApp` and add tests

* Extend coverage

* Wasn't planning to commit this yet

* Swap condition

Also point out that PKCS12 (.p12) keystores are now supported.

* add PivotTable unit tests

* obey the linter

* measure leftHeader cell content

* test cell data width detection

* obey the linter

* fix bad rebase

Add note about MongoDB.

* Cherry-pick `ModelPicker`

* Cherry-pick actions editor and form components

* Migrate from entity forms

* Remove `ModelPicker`

* Temporarily add "New > Action" flow

* Disable save button if query is empty

* Fix utilities moved

* Fix type errors

* Address comments

* Simplify `ActionForm` tests

* Break down `ActionCreator` props

* Add basic `ActionCreator` tests

* update action creator header gap styling

* Extract `convertActionToQuestionCard`

* Fix `CreateActionForm` ignores action name

* Fix `FormModelPicker` crash

* Address comments

* Remove "New > Action" flow

Co-authored-by: Ryan Laurie <iethree@gmail.com>

clarify that delete a database will also delete any questions/models/segments/metric that use the database in doc (#27707)

* fix throwing exceptions in handle-paging mw

* FE gets `value_field` for `/api/table/card__id/query_metadata`
by search the fields from calling `/api/table/card__id/query_metadata`.
if a field has id is a number, then use `field_ref`, else use `id`.

This commit add tests for that behavior

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

* Cherry-pick type changes

* Cherry-pick action endpoints

* Cherry-pick actions entity

* Fix type errror

* Fix type error

* Define `WritebackActionId` type

* Cherry-pick missing utilities

* Merge action types

* Update mocks

* Use testing utils

* Fix types

* Export action mocks

* Simplify `removeOrphanSettings`

* Fix timestamp names

* API for getting database usage

* use defmulti

* handle cases when database has no tables and add docstring

* sacrifice powerness in the light of beauty

* FieldValues skipping but not updating last used at

Related to #26863

When fieldvalues synching was being skipped, the
`get-or-create-full-field-values!` call was erroneously forgetting to
update the `last_used_at` time; the time was only being updated if new
field values came in since the last sync.

* Add test for inactive field values

* Only update last_used_at when there's an existing fieldvalues

- Use currency-specific decimals count (eg. 0 for JPY, 8 for BTC)
- Use plural currency names in Java, matching JS
    - previously: singular proper name "7.23 US Dollar"
    - now: plural prose "7.23 US dollars"
- "Small numbers" hack to treat min/max fraction digits as significant
  digits now applies to percentages under 1%, as well as the original
  |n| < 1

* Fixed regex for latitude name type matching

* Grouping regexes by lon/lat

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.

* updates + updates tests

- use titles for everything
- repeat "sounds" right
- biding time to remerge upstream

* Update src/metabase/util/malli/describe.clj

* pluralize times ouhgt to be private

* keep error messages in tests in sync 

* linter newline

* revert new tooltips for non-stacked series

* types

* restore aliases before annotating

* cleanup

* fix tests

* Don't add escaped->original if aliases have not changed

No need to walk and replace the aliases if they are identical. And in
that case, no need to keep a mapping of identical to identical. Not
super important but saves some time and complexity, and keeps other
tests passing since the presence of [:info :alias/escaped->original] in
the query caused them to trivially fail.

* oracle has a smaller limit and _expected_ mangled

previous testing behavior was "what happened" and not what should
happen. we fixed the bug but the "expect garbage" behavior was still
present

* Relax :alias/escaped->original schema

oracle tests use keywords for the alias

```clojure
{:alias/escaped->original
 {:test-data-venues--via-a763718f "test_data_venues__via__venue_id",
  :test-data-users--via--user-id "test_data_users__via__user_id"}}}
```

No idea why that is keyworded

* relax `:alias/escaped->original` schema

see previous commit