* Parallel QP tests; linter improvements; move QP test fns

* Cleanup

* Move query->expected-cols

* Fix QP test namespace

* Test fix 

* Fix merge issues

* Revert unrelated changes

* Test fix 

* Fix some things that are actually ^:parallel safe

* Remove Oracle logic for destroying DBs from different sessions since we don't test on AWS anymore

* Use ReentrantReadWriteLock for getting + creating test datasets to avoid race conditions

* Add non-`metabase.test` versions of things to the disallowed list for `^:parallel` tests

This change assumes that org.slf4j/jcl-over-slf4j is not really in use.

* QP: use Malli

* Fix schema names

* Fix missing namespaces

* Fix busted stuff

* Simplify the new schema

* Test fix 

* Test fixes 

* MongoDB fixes 

* FAST mu/defn

* Malli registry

* Misc fixes

* Some cleanup

* Misc cleanup and test fixes 

* mu/disable-enforcement

* Test fix

* Fix Cljs version of `disable-enforcement`

* Misc improvements

* Update tests

* Fix Kondo warnings

* Fix Kondo warnings

* Fix busted Malli schema

* PR feedback

* Fix busted schema

* Kondo fixx

* Test fixes 

* Use Malli version of `describe` now that PR was merged

* Work around https://github.com/metosin/malli/issues/924

* Test fixes 

* Improvements

* Test fix

* Migrate collection and permissions namespaces to Malli

* Fix docstring

* Fix Kondo warnings

* Bump org.apache.sshd/sshd-core to fix security alert

* Adapt metabase.util.ssh to new interface

* MLv2: Kondo linter improvements & cleanup

* Revert version bump

This reverts commit 9da0bd76.

* Calculate and set join alias when joining

* Use BuildJet runner for `be-cloverage`

We're seeing OOM failures in `be-linter-cloverage` job in CI.

* revert back to using ubuntu-22.04 and increase heap size to 2GB

* 2gb to 4gb

* add comment

---------

Co-authored-by: Ngoc Khuat <qn.khuat@gmail.com>

Commands can now specify a command-line arg spec to enable automatic argument parsing and improved help text.
New commands should use this arg spec format and existing commands can be updated if desired.

* Adds tools.cli command parsing and improved option behavior for v2 export and load
* Fixes --no-collections export, empty settings export
* Improves command error handling, adds help text on error
* Lists valid commands when unknown command is given
* Cleans up collection selection for generic export
* Supports --user by email in serdes v2 export

The core logic is still from the release script in bin/release.
The change here mostly wiring it up to GitHub Action so that it can be trigged
upon a new git tag (during the release process).

* initial changes

* add saml api

* address changes

* git restore enterprise/backend/test/metabase_enterprise/sso/api/saml_test.clj

* update comment

* update to have /api

* remove dbg

* fix alias

* change deps

* update test

* add test

* update test

* split tests

* add paren

This reverts commit 8a11e382.

The namespace `metabase.server.middleware.security` controls our content
security policy header. In dev we allow connections to 8080 for webpack
assets. Not dev we deny these.

`clj -M:run` is dev since it is running the project from source, not a
jar. This `mb.run.mode` was removed when we were fighting require issues
for `metabase.query-processor-test.test-mlv2`. That's solved so we can
restore the dev property to `:run`.

Added both FE and BE tooling for integration with LLMs, called "metabot". FE adds prompts for querying models and databases. BE takes these prompts, calls a LLM, parses the response, and returns the result.

* Add log4j dependency for custom json logging format

* Add ^:multipart option to defendpoint

(Allows file uploads)

* Add license information

* Add CDDL v. 1

Minor point version updates, including the redshift driver.

Updated module versions along with a few updated main deps.edn libs. Also added the outdated task to the deps file and fixed in place the nrepl and shadow-cljs nrepl ports.

Updated kixi/stats lib from 0.44 to 0.5.5.

* Moves to actively-maintained clj-yaml and removes obsolete pinned deps
* Adds discouraged namespace rule for clj-yaml (use metabase.util.yaml)

Co-authored-by: Braden Shepherdson <braden@metabase.com>

Added comments to org.mariadb.jdbc/mariadb-java-client and io.github.resilience4j/resilience4j-retry deps so we know what's blocking their upgrades.

Updated both the slf4j api and impl jars.

Upgraded com.snowplowanalytics/snowplow-java-tracker from 0.12.0 to 1.0.0. This did require refactoring the `metabase.analytics.snowplow` ns to use the new fluent API as well as suppressing eastwood linting of the ns due to a classloader issue as described [here](https://github.com/jonase/eastwood/issues/444).

* Reorganizes serdes v2 namespaces and some functions/multimethods to simplify implementation
* Updates serdes v2 to store/load :serdes/meta in YAML to remove ingestion path matching

All minor version dependencies have been updated to the latest. 3 libraries caused breakage and are documented here: https://github.com/metabase/metabase/issues/28967.

Calling our basis function with just :oss or :ee we don't end up with an
`:argmap` key.

```clojure
uberjar=> (def basis (create-basis :oss))
,#'build.uberjar/basis
uberjar=> (:argmap basis)
nil          ;; nothing extra in oss

uberjar=> (def basis (create-basis :ee))
,#'build.uberjar/basis
uberjar=> (:argmap basis)
{:extra-paths ["enterprise/backend/src"]}

;; and if other aliases are used:
uberjar=> (def basis' (b/create-basis {:project "deps.edn" :aliases [:dev :test]}))
,#'build.uberjar/basis'
uberjar=> (:argmap basis')
{:extra-deps {lambdaisland/deep-diff2 {:mvn/version "2.7.169"},
              methodical/methodical {:mvn/version "0.15.1"},
              io.github.metabase/hawk {:sha
              "45ed36008014f9ac1ea66beb56fb1c4c39f8342b"},
              ....}
 :extra-paths ["dev/src"...]
 :jvm-opts ["-Dmb.run.mode=dev" ...]
 :exec-fn metabase.test-runner/find-and-run-tests-cli}
```

* Fix flaky test and test for a new case

flaky test was annoying. It would timeout after 45 seconds. And
annoyingly, it times out on the _client_, not the server. So we don't
get the proper error message we expect.

And what's happening is that the backend just hooks up the pipe from
it's request to the response. And if no bytes ever come across, we just
twiddle our thumbs until the http request in the test gives up.

The only reliable way i could think of to fix this is to spin up a
webserver that just accepts and then ignores requests (which is what
github did to us in the flaky test).

Had to bump the ring adapter to get the newly exposed `:async-timeout
60000` parameter. By default the webserver in the test has a timeout of
30 seconds, which is shorter than the 45 second timeout for the test's
request to the geojson endpoint.

* add comment

* clean up test server logic

---------

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