* Make 'esc' button work with full page modal

* Rmv explicit bind

Users should follow instructions in our SECURITY.md file instead.

* Don't generate initial projections for MongoDB

* Massively streamlined MongoDB queries

* Linter/test fixes 

* Let's fix #13097 at the same time 

* add copy action to saved question

* Change text from "copy" to "duplicate"

Co-authored-by: Maz Ameli <maz@metabase.com>

* move clone action above archive action

* Use EntityCopyModal to dupe question

* update duplicate question cy test

* rmv unneeded line setting id to undefined

Co-authored-by: Maz Ameli <maz@metabase.com>

Merge x.38.0 -> master

* clarify pivot tables only work with simple and custom questions

* typo

* Maz edit

Co-authored-by: Maz Ameli <maz@metabase.com>

* picking your starting data

Co-authored-by: Maz Ameli <maz@metabase.com>

* Revert test-data-loading tweaks for now

* Test fix 

* Test fix

* Test fixes

* Unskip repro for #14859

* Test fix 



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

* Revert "Mb db connection uri parsing (#14716)"

This reverts commit b779333f.

* Readd the parsing of connection strings for db.env

#14854 Repro: Custom Expression using `case()` function fails when referencing the same column names [ci skip] (#14857)

#14843 Repro: Filtering a Custom Column does not give correct results when using "Not equal to" (#14847)

This issue is fixed on dc50e8a2
Closes #14843

Co-authored-by: Kyle Doherty <5248953+kdoh@users.noreply.github.com>

[ci skip]

#14776 Repro: Autocomplete results not correctly showing summary columns when full word entered [ci skip] (#14827)

* Group 2 repro versions into common describe block

* Unskip repro version 1 (fixed in #14804)

* Rewrite version 1 of the repro for #12985 using API

* Add version 2 of repro for #12985

* Semantic types migration

* Fixup for basic querying

* Remove the relation type migration.

it makes the diff far too hard at the moment. need to be able to just
move everything from special_type -> semantic_type and then correct
the few that look at it to care about the effective type.

the PK/FK stuff gets really invasive and needs to be in its own much
smaller changeset

* Just rename special_type -> semantic_type for first change

* Special type -> semantic type

* special-type -> semantic-type

* SpecialType -> SemanticType

* special type -> semantic type

mostly in documentation, docstrings, etc

* Fix tests which relied on order of sets

database position was annotated by map-index'ing over the
set. changing `:special-type` to `:semantic-type` changed the order of
the seq produced from it.

* special -> semantic in schema_metadata

* Tim is awesome: Undo overeager special->semantic in docstrings

* Un-rename semantic_type in data_migrations

These migrations are run unless a migrations table marks them as
already having run. If they haven't run, then the db is older and the
column is special_type most likely. So we let them run as
`:special_type` and add some error handling to the migration runner
that is _opt in_.

```clojure
(defmigration ^{:author "camsaul", :added "0.20.0", :catch? true}
  migrate-field-types
  ...
  )

(try
  (@migration-var)
  (catch Exception e
    (if catch? ;; catch? from metadata
      (log/warn (format "Data migration %s failed: %s" migration-name (.getMessage e)))
      (throw e))))
```

* Fix merged master changes

just accepted their changes and fixed up rather than fix conflicts.

* Search card queries

[Fixes #4227]

* Only show results with a non-zero score

* Don't pollute the namespace with search.config's vars

* Use a transducer to filter search results from the DB

It was fixed in #14804.

Merge `release-x.38.x` into master

Supporting "seconds", "minutes", and "hours" for relative date strings under "past", "next", "last", and "this" in the backend

Add the "minutes" and "hours" options to the frontend widget for relative date picker

Adding backend parsing tests for new options

Adding Cypress test to ensure new options appear in the relative date filter widget

Supporting "seconds", "minutes", and "hours" for relative date strings under "past", "next", "last", and "this" in the backend

Add the "minutes" and "hours" options to the frontend widget for relative date picker

Adding backend parsing tests for new options

Adding Cypress test to ensure new options appear in the relative date filter widget

* Add LDAP instructions + troubleshooting

* Update docs/administration-guide/10-single-sign-on.md

Co-authored-by: Jeff Bruemmer <jeff@metabase.com>

* Update docs/troubleshooting-guide/ldap.md

Co-authored-by: Jeff Bruemmer <jeff@metabase.com>

* Update docs/troubleshooting-guide/ldap.md

Co-authored-by: Jeff Bruemmer <jeff@metabase.com>

* Update a few lines

* A fully working example without any modifications

* Update docs/troubleshooting-guide/ldap.md

Co-authored-by: Jeff Bruemmer <jeff@metabase.com>

* Update docs/troubleshooting-guide/ldap.md

Co-authored-by: Jeff Bruemmer <jeff@metabase.com>

* Update ldap.md

Co-authored-by: Jeff Bruemmer <jeff@metabase.com>