* Avoid using `undefined` array when column formatters not specified

This led to `TypeError: Cannot read property "forEach" from undefined`
errors when no formatters were specified.

* Improve logging of unexpected errors during format compilation

* Log unsupported formatting operators and return a dummy operator fn

* Linting fixes

* Manually ES5-ify code that is to be executed by the Nashorn engine

Nashorn in JDK 8 only supports ES5.1.

* Update Rebuilt shared JS from `yarn build-shared`

* Move formatting foctory fns into an operator-indexed object

* Linter appeasement

* Test that all defined operators are supported in table formatting

* Flow annotations

* Return `null` in stead of `undefined`

Formatting/style changes snuck in.

* `yarn build-shared`

* Use operators from table formatting and not column filters

* use count as default new metric aggregation

* wip create GA default query

* flag metrics and segments that come from GA so we can filter them out/in

* fix test

* Fix drill through to question user doesn't have all data permissions for. Resolves #7928

* Fix flow

* Fix #10656

* Tests

* Fix lint + add a couple cute aliases

* fix object detail logic + add test

* fix issue preventing insights on year-grouped data

* remove (probably) unnecessary function

* formatting/style

* years are timestamps now

* allow for IconWrapper hover customization

* test / lint fixes

* Kill default server script because it’s broken

* set elb timeout setting

* Merge branch master into server_name-protection-is-dead
[ci skip]

* Add support for classification of NaN and -Infinity/Infinity doubles

These values are read correctly from the database, but after they are
serialized to JSON, don't get deserialized to a double object value,
but rather stay a string and cause failures.

This commit recognizes those values and will parse them as doubles.

Fixes #7779

* Update Redshift JDBC driver to 1.2.32.1056

relates to #9955

* Update metabase-plugin.yaml

Revert to previous behavior that uses `name` instead of `field_ref` for `field-literal` columns

When multiple instances run migrations race conditions are encountered that result in exceptions getting thrown. We try to mitigate this using auto-retry. The code in this PR is one more instance where a race condition can cause an exception, and it gets mitigated with an auto-retry.

* Log database connection error before humanizing it

The original, non-humanized error message may contain clues regarding the
error state, that might get lost in the humanization process.

* Log complete error at error log level

* Remove trailing colons from headings

* Reformat heading

* Add MySQL authentication troubleshooting

* Typo

* Reference MySQL 8 caveat in new MySQL section of admin guide

* Fix URL to troubleshooting guide section

* Update MySQL admin guide text

* "Fix" troubleshooting link

* Log database connection error before humanizing it

The original, non-humanized error message may contain clues regarding the
error state, that might get lost in the humanization process.

* Log complete error at error log level

* Don't lookup field ID for template tags, without a query

Based on snarfed/metabase@846f884

* Check for any falsey value instead of only `undefined`

* Mark `datasetQuery` parameter as optional

* Check for presence of `datasetQuery` only where it's being used

* fix cache timing bug

subtle issue where timing of reads and writes could fool a server into thinking it had the latest values when it didn't

* Filter out style properties with empty values

This caused CSS to break when `{:background-color nil}` was rendered as
`background-color: ;`.

* Use proper nil punning

* Convert `v` to string before passing to `seq`

* Fix locales newlines

* Bump Toucan version -> 1.14.0