* Increase log level to INFO from error

Closes #47396

logs before:
```
2024-08-29 08:37:03,836 INFO db.liquibase :: Checking if Database has unrun migrations...
2024-08-29 08:37:04,045 INFO db.liquibase :: Database has unrun migrations. Checking if migration lock is taken...
2024-08-29 08:37:04,047 INFO db.liquibase :: No migration lock found.
2024-08-29 08:37:04,047 INFO db.liquibase :: Migration lock acquired.
2024-08-29 08:37:04,167 INFO db.liquibase :: Running 83 migrations ...
```

logs after:

```
2024-08-29 08:39:45,019 INFO db.liquibase :: Running 83 migrations ...
...
2024-08-29 08:39:45,166 INFO liquibase.changelog :: ChangeSet migrations/001_update_migrations.yaml::v49.2024-06-27T00:00:00::calherries ran successfully in 0ms
2024-08-29 08:39:45,182 INFO liquibase.changelog :: Columns is_defective_duplicate(boolean) added to metabase_field
2024-08-29 08:39:45,182 INFO liquibase.changelog :: ChangeSet migrations/001_update_migrations.yaml::v49.2024-06-27T00:00:01::calherries ran successfully in 14ms
2024-08-29 08:39:45,199 INFO liquibase.changelog :: Custom SQL executed
2024-08-29 08:39:45,200 INFO liquibase.changelog :: ChangeSet migrations/001_update_migrations.yaml::v49.2024-06-27T00:00:02::calherries ran successfully in 16ms
2024-08-29 08:39:45,202 INFO liquibase.changelog :: Foreign key fk_field_parent_ref_field_id dropped
2024-08-29 08:39:45,202 INFO liquibase.changelog :: ChangeSet migrations/001_update_migrations.yaml::v49.2024-06-27T00:00:03::calherries ran successfully in 1ms
2024-08-29 08:39:45,204 INFO liquibase.changelog :: Foreign key constraint added to metabase_field (parent_id)
2024-08-29 08:39:45,205 INFO liquibase.changelog :: ChangeSet migrations/001_update_migrations.yaml::v49.2024-06-27T00:00:04::calherries ran successfully in 2ms
...
```

* empty commit to bump CI

Better metabot logging, especially around generated token counts. This will be particularly useful as we determine what size of prompts we can generate.

* Switch to Toucan 2 part 1

* Fix Kondo errors

Upgrade Liquibase to latest version; remove final Java source file and need for `clojure -X:deps prep` (#20611)

* Upgrade Liquibase to latest version

* Try adjusting log

* Fix checksums for the TWO migrations with ID = 32

* FINALLY get Liquibase to use Log4j2

* Set Liquibase ConsoleUIService OutputStream to null OutputStream

* Manually define a package for our H2 proxy class so Java 8 works

* Fix package-name determination code

* Update migrations file spec

* `databasechangelog` shouldn't be upper-case

* Lower-case quartz table names

* More MySQL fixes 

* Properties for all the Quartz tables 

* Formatting tweaks [ci skip]

* Revert a few more busted changes

* Fix more busted changes

* Bump Liquibase version to 4.8.0 to fix MySQL defaultValueBoolean bug

* OMG I think I finally fixed MySQL

* Remove Java source file and prep-deps code

* Remove two more references to bin/prep.sh

* Minor cleanup

* Revert unneeded changes

* Fix busted indentation

* Don't search inside java/ anymore since it's G-O-N-E

* Appease the namespace linter

* Update src/metabase/db/liquibase/h2.clj

* Determine MB project root directory relative to source directory of build scripts

* Support calling build-driver! as a -X fn, and support dirs outside of modules/drivers

* Support loading 3rd-party driver manifest files at (dev) launch

* Fix log4j not working on latest version of CIDER (unrelated)

* Fix dissoc

* project-root-directory is supposed to be a string

* Explicitly specify %throwable in Log4j logging pattern so the ex-data gets printed

This tweaks means Exceptions get rendered for logging with .toString instead .getMessage.

See https://github.com/clojure/tools.logging/tree/31073fe1fbb0533f3c775fa667de70809f24b127#log4j2
and https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns

* Remove ad-hoc query perms check on save logic from metabase.models.card.

We already do this in metabase.api.card, so in practice this is redundant code.

* Better permissions exceptions when missing ad-hoc perms for creating/updating a Card

* Fix #11719

* Return more info with most API exception responses

* Add tests for #11719 and #14931

* Fix namespace lint errors

* Fix error message grammar (thanks @jeff303)

Changing the namespace name of the logging middleware broke access
logging. Changing this config file to the proper namespace for logging
makes it happen again

See #14773

* Fix collections/graph stack overflow

* Test fixes 

 [ci postgres] [ci mysql]

* Show engine in Task trouble shooting logs (#13608)

* Show engine in Task trouble shooting logs

in an effort to get better feedback when people raise issues about
long running sync processes, include the database engine in the logs.

Also wrapped `th` in a `tr` inside the `thead` to remove react warning

* Const intead of let on the db_id_to_engine

* Swap db id for db name

* Move comment out of jsx

* fixup! Merge branch 'release-x.37.x' into fix-collections-graph-stack-overflow

Co-authored-by: dpsutton <dan@dpsutton.com>

Avoid ansi output from log4j2 so that the environment variable NO_COLOR
behaves as expected.

Even though this Appender wasn't referenced anywhere, it still
initialized. Commented out this appender so it can be used as an
example, but it won't create a folder called ${logfile.path} now

Resolves #13422

We should not be logging to a file by default, this was an oversight in
the migration to log4j2

Resolves #13422

* Upgrade to log4j 2.13.3

Upgrades us to newer Log4j

Resolves #12719

* fixing reflection warnings

* reflection warning on test

* make tests work

took a while to figure out how to configure log4j properly
programatically - it's not as easy as log4j 1

add logging adapters for commons-logging, slf4j, liquibase, etc so that
all logging routes through log4j2 now

* appease the linters

* okay cljr-clean-ns makes this line too long, I get it

* add log4j2.xml config for Cypress tests

* update log4j configuration file documentation

update which flag is used by the backend tests

[ci all]

* update cheshire because clj-http updated

* Wire up the metabase-appender to Log4j2

This was brutal to figure out - log4j usually silently fails, so it took
finding the right combination of configuration settings and system
properties to get it to log enough to find out why the appender was
never invoked.