* upgrade some deps to fix warnings

* add back lint-yaml scrip

* remove e2e/karma references

* Add repro for #13235 [ci skip]
(Cannot filter by selecting remapped display value from dropdown list)

* Fix obsolete MBQL syntax in `localization.cy.spec.js` [ci skip]

Introduced in: https://github.com/metabase/metabase/commit/6b5765718daff384a1831cd7383401369b8c1725.

* Fix obsolete MBQL syntax in `dashboard.cy.spec.js` [ci skip]

Introduced in: https://github.com/metabase/metabase/commit/2958b836cc73c16b74b6e6e8fd96a6dabd12f60e.

* Fix obsolete MBQL syntax in `nested.cy.spec.js` [ci skip]

Introduced in: https://github.com/metabase/metabase/commit/ab762e1ffb8cd79fedc050709c059e8c8b87ef9b.

* Fix obsolete MBQL syntax in `dashboard-drill.cy.spec.js` [ci skip]

Introduced in: https://github.com/metabase/metabase/commit/cb4371e9fcc45ec242d106c4a01c4a0d68d4c324.

* Fix obsolete MBQL syntax in `nulls.cy.spec.js`

Introduced in: https://github.com/metabase/metabase/commit/854f5317df724abc0a6026b06bfa539d15d34fa6.

* Add positive assertion for repro for #13571

* Add repro for #12872 (Between Dates filter behaves inconsistently based on whether the column is from a joined table or not)

When a database is updated via the admin interface, any sensitive data
(private keys, passwords, etc) should be handled on an "upsert" basis -
only modify those fields if they were changed from the "protected
password" value.

This affects all database drivers.

Resolves #13442

* Fix collections/graph stack overflow

* Test fixes 

 [ci postgres] [ci mysql]

* Show engine in Task trouble shooting logs (#13608)

* Show engine in Task trouble shooting logs

in an effort to get better feedback when people raise issues about
long running sync processes, include the database engine in the logs.

Also wrapped `th` in a `tr` inside the `thead` to remove react warning

* Const intead of let on the db_id_to_engine

* Swap db id for db name

* Move comment out of jsx

* fixup! Merge branch 'release-x.37.x' into fix-collections-graph-stack-overflow

Co-authored-by: dpsutton <dan@dpsutton.com>

Merge master into release-x.37.x 10-29-2020

Migrate build/upload Elastic Beanstalk artifact code into main release script and other improvements (#13635)

* Always use current branch; determine CE vs EE build based on version number

* Rename delete-file! -> delete-file-if-exists!

* Dox & TODO message

* Move draft release template

* Some logging tweaks for deleting files

* Move s3 upload code to common namespace

* Integrate EB artifact logic

* Move .ebextensions -> release

* Remove old EB release scripts

* Update obsolete repro for #12985

* Remove `funnel_add` icon

* Put yaml-lint into devDependencies

That way, the CI run is more reproducible (no need to install yaml-lint
on the fly).

* Attempt to lint YAML files via yarn run

* Update the CI workflow dependency for yaml-linter

* Show engine in Task trouble shooting logs

in an effort to get better feedback when people raise issues about
long running sync processes, include the database engine in the logs.

Also wrapped `th` in a `tr` inside the `thead` to remove react warning

* Const intead of let on the db_id_to_engine

* Swap db id for db name

* Move comment out of jsx

* Fix failing Cypress test in `dashboard-drill` spec file

* Assert that the page content rendered (as per @dacort 's suggestion)

* [Fixes #11879] [Fixes #8410] Don't wrap email attachment filenames

* Non-ASCII characters in filenames are encoded [as per IETF RFC
  2047](https://tools.ietf.org/html/rfc2047) (c.f. #8410)
* Sufficiently-long _encoded_ filenames are sent over multiple lines
    as per [RFC 2184 section
    3](https://tools.ietf.org/html/rfc2184#section-3), for example:

    ```
    Content-Disposition: attachment;
      filename*0="=?UTF-8?Q?T=C3=A9=C5=BFting_non-ASCII_=C4=8D=C4=A5=C3=A4ract";
      filename*1="ers.xlsx?="
    ```
* Many mail clients do the right thing, but Gmail does not

This commit therefore turns off wrapping, as per [Bill Shannon's
Stack Overflow answer re. an undocumented system
property](https://stackoverflow.com/a/53344141/220529)
(Bill Shannon co-wrote the Java email library, which is used by postal
(the Clojure wrapper we use).

* (Hopefully) fix race condition in dashboard drill Cypress spec

Suggested by @flamber

* Skip flaky Cypress tests (per Nemanja)

* Only set `mail.mime.splitlongparameters` once

* Adds dev/src/dev/nocommit to ignore file [ci skip]

now you can create a folder nocommit/ under the dev classpath root so
you can keep some namespaces around as you work on features.

Ex:

```clojure
(ns dev.nocommit.oom
  (:require [metabase.models
             [database :refer [Database]]
             [field :refer [Field]]
             [table :refer [Table]]]
            [metabase.sync.analyze
             [fingerprint :as analyze.fingerprint]]
            [metabase.sync :as sync]
            [metabase.sync
             [field-values :as sync.field-values]]
            [metabase.models.field-values :as field-values]
            [metabase.sync.analyze.fingerprint.fingerprinters :as fingerprinters]
            [metabase
             [util :as u]]
            [metabase.sync.sync-metadata.fields :as metadata.fields]
            [metabase.sync.sync-metadata.fields.fetch-metadata :as fetch-metadata]
            [metabase.query-processor :as qp]
            [toucan.db :as db]
            [metabase.db
             [metadata-queries :as metadata-queries]]))

(def pg (Database 4))

(comment
  (fetch-metadata/db-metadata pg emails-table)
  (metadata.fields/sync-fields! pg)

  (sync/sync-database! pg))

(clojure.test/run-tests 'whatever-namespace)

```

I ended up with lots of `(comment ...)` blocks in lots of different
namespaces and this has helped keep my worktree clean.

* Empty commit to trigger CI [ci skip]

skipping ci thought so hopefully the checks on Github are satisified.

* Repro for #13571: Display rows whose value is `null` (#13591) [ci skip]

* Reproduces #13571 

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

* [[null]] is a valid response

Previously, this said that a result of `[[null]]` was an empty result
set, but in reality, it's a valid result set of a single column with a
null value.

Resolves #13571

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

* Specify location on getQueryResults calls (#13592)

You must specify the location on any getQueryResults calls to BigQuery.
It's supposed to be optional for anything but EU and US regions, but
useast1 seems to require it.

Fixes #13582

[ci bigquery]

* v0.36.8.2

Co-authored-by: Robert Roland <rob@metabase.com>

* Reproduces #13571 

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

Repro for #13062: Multiple dashboard filter values not parsed on drill-through (numeric values) (#13580)

* Add repro for #13062: Multiple dashboard filter values not parsed on drill-through

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

just bumping the driver gets us the GEOGRAPHY type in the snowflake
types enum. We mark it automatically as `:type/*` but can do better
marking as `:type/SerializedJSON`.

Results look like (from metadata-queries/table-rows-sample)

```clojure
[["1"
  true
  #t "2020-10-23T00:00"
  1
  "{\n  \"coordinates\": [\n    0,\n    0\n  ],\n  \"type\": \"Point\"\n}"]]
```

and field information:

```clojure
{:name "E",
 :id 1857,
 :special_type :type/Category,
 :database_type "GEOGRAPHY",
 :base_type :type/SerializedJSON}
```

```sql
create or replace table metabase_bug (
    a string,
    b number,
    c boolean,
    d timestamp_ntz,
    e geography
);

insert into metabase_bug values
    ('1', 1, true, current_date(), 'POINT(0 0)');
```

Wait for initial query to be ready before paginating

When pagination was added, we were requesting the first page before it
was ready. This adds a job completion wait on the initial query before
we start retrieving pages.

Resolves #13582

[ci bigquery]