* explanation and connective tissue

* heading promotion

* formatting

* note on full-app embedding

* hyphen

* Fix input widget with parameter using incorrect type

When a FieldValuesWidget as `parameter` prop, it indicates that it is
tied to a dashboard parameter, so we should use parameter instead of
field type when rendering the component.

* Add a test

* Address review

* Remove wrong JSdoc types

* Fix failed E2E test due to wrong mock parameter type

* Merge follow-up and abandonment emails

* Update the call to action

* Remove unused requires

* Remove all traces of abandonment emails

* Remove unused require

* source -> values_source for parameter

* Rename FE source type & options

* ParameterSourceOptions -> ValuesSourceConfig

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

* Handle abbreviation and date-separator in a fn, where defaults are passed in in any place where nil COULD exist

Moving abbreviation and date-separator string changes into a post-processing fn allows each unit case to handle the
date-style default formatting, and eliminates the problem of date-style being `nil` in the let statement. It was this
scenario where `abbreviate` was `true`, but `date-style` was `nil`.

In many cases, if `date-style` is nil, then so is `abbreviate` and `date-separator`, in fact, the default from the
frontend sends nil for all of these keys. In such a case, none of the branches run and nil is safely passed
through. It is then handled appropriately with `(or ...)` expressions in each entry for the case statement.

But, it is indeed possible to have a nil `date-style` with non-nil `abbreviate` or `date-separator` keys. Now, the
post-process-date-style function is only ever called AFTER the default date-style is set in whatever case branch is needed.

* Turn frontend day format 'dddd' into backend format 'EEEE'

The frontend sends a datetime format string to the backend and some elements are not equivalent to the expectations
the java datetime formatter has.

* Unskip e2e reproductions

* Add a test for all 'written date' combos

* These tests fail b/c I fixed the 'default' from Abbreviated to non-abbreviated

* Add test 'matrix' for numerically formatted dates, and each separator

* Finally, add tests to confirm that custom-formatting is applied

This adds a cross-platform number formatting library in CLJC, which has
(nearly) identical output in both JVM and JS environments.

The only known differences are:
- JVM Clojure has `BigDecimal` support, so isn't limited to a `double`'s
  range.
- Exact spelling/capitalization of the full names of currencies differs.
    - JVM: "7.34 US Dollar"
    - JS: "7.34 US dollars"

Some future work is required to fully land this. In particular, the
`currency_in_header` logic should be moved to the table formatters, not
implemented on the JS side of this change.

* Adding Subtitle to Series Name Input

* PR Feedback

* fixing cypress test

* use null coalescing operator to allow numeric zero values

* add tests

* update storybook types

* Start-of-cycle 46 basic dependency version bump

Some dependencies with available major version bumps are only updated
to the latest minor version of the current major version. Some
additional dependencies will be updated in future PRs.

* Removes commons-lang from sparksql deps exceptions

* Fixes MongoDB SRV test for monger 3.6.0

* fixes SQLite datetime tests for new driver version 3.40

* 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

* error on null user attributes

* fix test

* Add sparksql datetime-diff

* Set supports-timestamptz-type? to false for sparksql

* Refactor sparksql datetime-diff

* Change float to int

* Add datetime-diff for h2

* Set supports? to true

* Refactor h2 datetime-diff

* Formatting

* WIP

* One more

* bump apache poi

* bump docjure

* Fix typo in log.clj

formating -> formatting

* Update src/metabase/server/middleware/log.clj

som -> some

Co-authored-by: flamber <1447303+flamber@users.noreply.github.com>

Co-authored-by: flamber <1447303+flamber@users.noreply.github.com>

* Rename `errors` to `validation`

* Add `GenericErrorResponse` type

* Add `getResponseErrorMessage` helper

* Use new helper in `use-form-submit`

* Handle incomplete error responses

* Use new helper in `FormikForm`

* Make `getResponseErrorMessage` accept `unknown`