When an MBQL query has an order by for a column that has been
remapped via FK, it will swap the order by for the original field for
the remapped field. Previously this would order by the original source
column and apply that to the remapping which would be unexpected.

If we have an external remapping, human_readable_field_id is
required. We now return a 400 if that is missing.

Currently this is used similarly to category. As we get more remapping
features (booleans, strings etc) this will be different from
categories and won't have the existing category baggage.

One of the tests added recently changes the special_type of
category_id. It should have save what it's original value was and
restored it after it was done instead of assuming it's previous value
was nil.

Fix abrupt scroll in data reference section segment picker

update ga metadata

Metabase-lib

clean up checkbox component

Docker H2 to Postgres migration documentation

This makes the query_metadata route behavior similar to the field
values route.

This reverts commit 95a65d42.

nested queries data picker styling