Since it needs to grab the built JAR anyway, it's faster to obtain the
version.properties from the JAR.

This shaves off approx. 1 minute from Percy CI run.

There's no point of processing files via ESLint loader when building
for production. If there's any linting issue at all, it should be
caught with a different CI run.

This shave off >2 minutes from Uberjar build (front-end step).

Development/hot-reload isn't affected at all.

Show how to increase Jetty verbosity

* Update docs/operations-guide/log-configuration.md

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

- Make all specific problems H2-level headings.
- Create a `doc-toc` div at the top for the table of contents.
  - Don't use `learn-doc` because we may want to style/show this one independently.
- Link to all problem headings.

Note: can't use metadata in a page header because our CI tools splat their own headers into these pages, so anything we add becomes part of the page body.

* Add sane defaults to the card size in `createQuestionAndDashboard` custom command

* Add repro for #17212

Adding new cache to `metabase.driver.sql-jdbc.connection` that tracks the DB details hash values per DB id

Checking if the non-empty hash value of DB details changed in `db->pooled-connection-spec` in order to invalidate an existing pool

Adding test that redefines the log fn to assert that the pool is invalidated on hash change

It's redundant since the job explicitly installs the proper version in
the previous step, and also running that prematurely pulls a bunch of
JARs from Maven Central.

This should shave 20 seconds from the CI runs.

* Add parial repro for #15656

* Update frontend/test/metabase/scenarios/onboarding/about.cy.spec.js

Co-authored-by: flamber <1447303+flamber@users.noreply.github.com>

* Bump some more backend dependencies

* Add license info for com.sun.activation/jakarta.activation

* Fix reflection warnings

* Revert bump of MariaDB for now

Remove the `driver/can-connect?` implementation and move the `select-keys` logic instead to the existing place in `sql-jdbc.conn/connection-details->spec`

Update test to also include the `:let-user-control-scheduling` details entry

* Bump some backend deps.

* Update i18n/locale to work with new version of LocaleUtils

* Fix JUnit output not correctly stripping ANSI color codes

* Remove find-tests profiling log message

* 1-arg arity of metabase.test-runner/run

* Fix bug with metabase.test-runner/find-tests with a single test name

* Fix location of share icon

* Update 12-public-links.md

Differentiate between dashboard and question sharing

Co-authored-by: Luis Paolini <paoliniluis@gmail.com>

* Remove last of leiningen, comment in shadow and lsp cp [ci skip]

* empty commit to flush [ci skip]

* remove moderation reviews hydration

* Restore hydration of moderation_reviews and handle correctly

nested hydration is (i think) positional. So if you get something
handed to you you must return something in that position. Prevoiusly
was removing nils and then returning a smaller collection of hydrated
items (cards here). But this meant input might look like this

[card1 nil card2] and return [card1 card2] and in the nested hierarchy
things didn't get matched up correctly.

In the real world application it might look like this:

```clojure
{:ordered-cards
 [{:card-id 1}
  {:card-id nil
   :viz-settings {info-for text-card}}
  {:card-id 2}]}
```

And the nil card comes into this function and we return them in a
strange manner things get wonky

* Remove `project.clj` from Percy workflows

* Replace `project.clj` with `deps.edn` in `build-for-test` script

* Update reference to the `project.clj` in the comment

We're playing this whackamole because we added the middleware to universally sorta stomp on any `limit` or `offset` params, and they got stomped on. Which, in turn, led to my PR to make the default not limited. Which, in turn, led to the other issue this PR solves which makes the search things we relied upon to not have a limit, have a limit.

* Register `@testing-library/jest-dom/extend-expect` globally

* Remove unnecessary imports from unit tests

* Add some dox

* Rename test-runner & cloverage -> metabase.test-runner & metabase.cloverage-runner

* Move JUnit-related test runner code to separate namespace

* Bespoke JUnit-output code

* Delete unused .lein-classpath file

* Do JUnit writes in a cached thread pool

* Add failing test to make sure JUnit output works as expected...

* Move bad-test to metabase.bad-test so the FAILING tests actually run

* FASTER TEST LOADING 

* Test CircleCI :system-out

* Final cleanup (hopefully)

* Sort some namespaces; allow initializing :plugins when namespaces get loaded for now.

* Need those [[tags]] in docstrings

* Fix bad docstring