* update yamls for latest change on key order

* bring custom reports back

* add Metabase Analytics instance type

* add new view v_tasks, iterate content adding links

* add v_tasks to permissions

* fix double precision types for h2 and mysql

* add type to instance analytics col

* add mysql rollback

* fix paths in migration

* handle dynamic tab ids

* update yamls click behavior

* add namespace=analytics to audit collection

* add type to collection

---------

Co-authored-by: Noah Moss <noahbmoss@gmail.com>
Co-authored-by: Ryan Laurie <iethree@gmail.com>
Co-authored-by: Noah Moss <32746338+noahmoss@users.noreply.github.com>

* Unskip previously quarantined pie chart nulls test

* Update card details

* QueryBuild and SQL questions: hide Explore results with parameters
* Fix AtomicQuery.canNest return type (so that it is always boolean)
* Add Question.canExploreResults tests

Co-authored-by: Ngoc Khuat <qn.khuat@gmail.com>
Co-authored-by: Cal Herries <39073188+calherries@users.noreply.github.com>

adds new `ascendants` multimethod, which traverses tree upwards w/o looking for children.

Pulse and related are skipped for now: they have a full serialization support, but are not serialized.

* Adjust mysql container env

* Setting the HOST can cause trouble they said

https://hub.docker.com/_/mysql. Let's try it without then.

* Also MYSQL_USER doesn't play well with empty password

* Cast results of temporal extract to decimal

* Update test

* Update test

* Revert casting temporal-extract results to decimals

* Handle mysql YEAR type as a number instead of a date

* Cleanup

* Use mongo sessions in aggregation pipelines

Using sessions, cancel signal from streaming response can be handled
correctly - query is killed also on database side.

* Update tests

* Let the middleware handle the exception

While coding the other test, I've found out that if exception is handled
in the `reducible-results`, code clogs for 3 minutes,
which is `.maxTime` for aggregation. I don't know the exact reason yet,
but for time being I'm leaving the exception handling to middleware.

* Add testing string

* Encode aggregation results as `BasicDBObject`

Use this type instead of BSON's Document because code transforming
DBObject to clojure structures is already in place.

* Update exceptions handling and tests

Exception handling now more resembles code in other drivers. Tests were updated
to use mbql query instead of raw native to avoid differences between various
mongodb versions. `$dateTrunc` was not available in version 4.

* Increase cancelation interval in tests

* Address remarks and update test to handle cold start

By cold start I mean running it before dataset is initialized.

* Remove unnecessary hint

See #35878 which did the same for `column-filter` drills.

This reuses the logic from that PR to include the same information on
`quick-filter` drills as well. Most quick filters are a single click,
but there are a few special cases that are more involved and require
showing a complete filtering UI.

This renames `lib.js/column-filter-drill-details` to
`lib.js/filter-drill-details` as well.

---------

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

* Fix and unskip the previously quarantined audit v1 test

* Improve assertions

* [MLv2] Short name display for filter clauses

Fixes #35752

Built for the timeseries widget and the associated operators. Generally
shows the user selected dates and occasionally shows an operator.
The choices are about what looks correct more than following particular
rules.

* fix newline

* Update Admin User Form to use Formik

* typing LoginAttributesWidget

* Making first and last name not required

* PR Feedback

* adding unit tests

* fixing email selector

* Update parameter input styles
* Remove unused class
* Remove unused flex-basis

We started running audit tests in the CI again, but forgot to
remove this file.

* Unskip previously quarantined test

* Improve test readability

disable submit button if form is unchanged, and fix spacing

When loading from a backup, we should not fail if the previous version saved keys that are no longer needed in the
current version. This adds a step (after ingestion but before loading) that removes any "extra" keys from the ingested
entity.

How?

- make `load-xform-basics` remove extraneous keys from the ingested model.

- by default, it identifies the "extraneous keys" as keys *other than* keys corresponding to column names in the database.

- for *some* ingested models, there is not a 1:1 correlation between an ingested model and a `:metabase/model`. For example, when we ingest an `"Action"`, that corresponds to the `:model/Action` model. But that model has three "submodels" - `:model/QueryAction`, `:model/HttpAction`, and `:model/ImplicitAction` - and when we load the ingested map into the database, `action/insert!` will insert subsets of the map it receives into _two_ tables (`action` plus one of the submodel tables).

- to handle this case, `serdes/ingested-model-columns` is a multimethod, which we can override. For example, for `"Action", we override it to include the full set of columns that exist in any of the model/submodel tables.

Co-authored-by: bryan <343288+escherize@users.noreply.github.com>

If this drill is targeting an aggregation column, the query needs an
extra stage added. To enable the custom filtering UI, this (possibly 
updated) query, stage number, and the correct column
*in that new stage* are returned as part of the opaque `column-filter` drill.

`lib.js/column-filter-drill-details` is added to hand those details
to the FE as a JS object containing opaque CLJS values.

* Unskip previously quarantined test

* Fix lint errors in subscriptions test

* Fix lint errors in the alert test

resolves #30133 and #30134

extracting was fixed in 0f1c1943, also resolves #35880

* Re-enable custom mapping null values test

* Remove misleading comment

* Address review comments