* Add `SnippetCollectionForm`

* Add `SnippetCollectionFormModal`

* Use new form

* Remove old form

* Clean up snippet collections entity

* Fix submit button title

* Fix initial values

* Move the config-from-file code into the advanced-config directory since that's the feature we want to flag on

* Always apply the :settings section first in the config file

* config-from-file should check that we have a premium token with the :advanced-config feature

* Sort namespace

* Settings does not have to come first anymore

* Remove empty `binding` forms

* Test fix? 

* Test fix? 



* Fix failing tests, for real this time

* Revert "Fix failing tests, for real this time"

This reverts commit 0a57055b1be249d9ba5b6b6ebe4f163e1f21e2b2.

* Don't make the tests parallel since that breaks other stuff

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

There are now three top-level trees:

- regular `collections/path/to/collection/...`
- `:namespace :snippet` collections in `snippets/path/to/collection/...`
- `databases/mydb/schemas/PUBLIC/tables/customers/fields/name.yaml`

The path for any given entity is determined by the
`serdes.base/storage-path` multimethod.

On the ingestion side, things are a bit tricky because the paths don't
map directly to `:serdes/meta` hierarchies anymore. Instead each model
registers a function to turn a file path into either a `:serdes/meta`
hierarcy or nil for a bad match.

Ingestion will fetch all these functions once and then try them all in
arbitrary order until one matches.

* Add basic `CreateCollectionForm`

* Add `CreateCollectionModal`

* Use new form in "New" menu

* Remove no longer needed `onChangeLocation`

* Use new form in collections ellipsis menu

* Add unit tests

* Don't use legacy form lib in collection plugin

* Add `canManageCollectionAuthorityLevel` utility

* Update `FormCollectionAuthorityLevel`

* Add authority level field to new collection form

* Remove old collection form

* Tweak how authority level form field is exposed

* Convert authority level plugin to TypeScript

* Don't use `any` too much

* Clean up setting selector wrappers

* Sort `LicenseAndBillingSettings` imports

* Use `getSettings` in `LicenseAndBillingSettings`

* Fix selectors usage in metabase enterprise

* Fix selectors usage in Slack forms

* Fix selectors usage in `GoogleAuthForm`

* Fix selectors usage in `AppBanner`

* Fix selectors usage in `CloudMigrationHelp`

* Unsubscribe query builder from app settings

They don't seem to be used at all

* Fix selectors usage in auth selectors

* Fix selectors usage across the app

* Fix something happened to an import

This was breaking Metabase's understanding of foreign keys after
deserialization.

Card, Dashboard, Dimension, Metric, NativeQuerySnippet, Segment and
Timeline all now using their `:name` fields for the file label.

File names should now be more human-friendly.

* Move the config-from-file code into the advanced-config directory since that's the feature we want to flag on

* Always apply the :settings section first in the config file

* Apply suggestions from code review

Co-authored-by: metamben <103100869+metamben@users.noreply.github.com>

Co-authored-by: metamben <103100869+metamben@users.noreply.github.com>

This also changes the semantics of
`metabase.models.serialization.base/load-find-local` to return the whole
entity, not just the ID. `load-one!` always needs the whole entity (if
it exists) anyway, and some of the `load-find-local` implementations had
the entity already loaded but just passed along the ID. This saves some
double lookups, especially for inlining eg. `DashboardCard`s under
`Dashboard`.

Move the config-from-file code into the advanced-config directory since that's the feature we want to flag on (#26461)

* [:field-id id] => [:field id nil] or $name. Except places where tests
are meant to check normalization

* [:datetime-field [:field id] unit] -> [:field id {:temporal-unit unit}]
or !unit.name

* [:fk-> [:field 1] [:field 2]] => [:field 2 {:source-field 1}]

* Uses all text scorers in the final result

- instead of just the maximum one
- add tests

* add prefix scorer test + fix text-score-with

* linter fixes

* pass in number of results to find

* refactor test function

* fix linter by removing unused namespace: metabase.util

* limit arity of serialize to 3

* make oss-score and ee-score different things

- They were defined to be exactly the same, but should be different!
- Update some tests that broke when a test function was fixed

* remove extra let

* move rseq back out of sorted-take

* improve test feedback

* force weight of text based scorers always weigh 10

* handle 0 score/weights when normalizing scores

* add nil check

* fix more subtle test differences

* more test fiddling

- still test that :offset and :limit respect limits

* reuse bit->boolean from api collection

* clean up some tests

- filter -> remove
- replace some magic numbers
- revert to testing entire maps instead of names of sorted items

* add test, docstring, and weight

* sort ns requires

* responding to most of the review comments

* start our zero-score sum check with 0

* do not tokenize / normalize nil raw-search-string

* force equality in basic search test

* modify test to work in dev and test environments

* use display_name in results when appropriate

- This was looking for the _first_ column that had a non-zero score, but
actually we need to consider all relevant columns.
- Uses them to figure out if there is a display name, and if there is,
to use it.
- Coppied over the logic about showing :context from the prior approach

This allows smaller selective exports that (for example) don't need to
include the data model if you know the other side has it.

This makes deserialization faster since entity_id columns are indexed.

Mostly this was caused by `:id [:in []]` empty lists if eg. you don't
have any non-personal collections, or no dashboards exist.

Also I broke the argument passing to the selective dump command
`extract-subtrees` a while back and this fixes it.

Fixes #26043.

* Move metabase.config.file code => enterprise directory

* Support setting Settings in config.yml

* Support disabling database sync in config files

* Setting name has to be a keyword since that's how YAML gets parsed

* Test fix 

* Settings have to be keywords

* Fix Kondo error

* Fix Kondo errors

* Fix Kondo errors

* Remove unused namespace

* Config from file: fix User upsert not hashing password

* Move metabase.config.file code => enterprise directory

* Support setting Settings in config.yml

* Setting name has to be a keyword since that's how YAML gets parsed

* Test fix 

* Fix Kondo error

* Fix Kondo errors

* Remove unused namespace

* Move metabase.config.file code => enterprise directory

* Support setting Settings in config.yml

* Setting name has to be a keyword since that's how YAML gets parsed

* Test fix 

* Fix Kondo error

* Fix Kondo errors

* Remove unused namespace

* Move metabase.config.file code => enterprise directory

* Test fix 

* Fix Kondo error

* Fix Kondo errors

* Remove unused namespace

This makes them less likely to collide, which was a problem on some
larger instances.

A following PR will generate entity_id from the hashes before
(de)serialization, allowing for easier merging later (since entity_id is
indexed in the database).

Add `saml-configured`, `jwt-configured` and `google-auth-configured` settings, and some general setting refactor (#26045)

* general sso configured/enabled setings refactor

* fix ts type error and update be tests

* Add created_at to Collection

* Simplified migrations [ci skip]

* Add SQL for H2 and MySQL; add tests

* Sort namespaces

* Test fixes 

* Test fixes

* Test fixes 

* Make sure MySQL/MariaDB Liquibase generator sets the current timestamp function for ADD COLUMN

Previously, some automatic behavior was causing problems in serdes.
(The worst example is generating an `entity_id` on insert while
deserializing an entity we don't own - if deserialized again it would be
duplicated.)

A whole cascade of design choices fell out of this problem:
- `insert!` would generate `entity_id`s, so use `simple-insert!`
- But `simple-insert!` doesn't convert eg. MBQL `:definition` maps back
  into JSON strings
- We got the maps as Clojure data and not JSON strings because `select`
  and `simple-select` both run `post-select` and parse the JSON.
- So we ended up with a raw query on the select side and `simple-insert!`
  on the storage side.

This change unwinds that whole stack, and instead uses a dynamic
var to suppress the few pieces of `pre-insert` and `pre-update` logic
that causes problems.

The end result is much cleaner, and much more consistent with the rest
of Metabase's backend logic.

* [Apps] Remove emitters

Emitters were created when we thought that we would be adding actions to
multiple places in metabase. Instead we've coalesced to actions being a
core feature of data-apps and are executed from within them. Attaching
actions to models, as a form of re-use rather than a form of execution,
means that actions can still be executed directly from a model, if we
want to allow that in the future.

* Fix lint errors

* Move perform-action! tests out of the api.

Since we want to keep the implicit bulk functionality but remove those
endpoints move the tests to the actions namespace.

* Fix linter

* Change driver test to use function instead of endpoint