Added  MB_JDBC_DATA_WAREHOUSE_UNRETURNED_CONNECTION_TIMEOUT_SECONDS to docs

* Add `align-temporal-unit-with-param-type-and-value` multimethod

* Fix tests and add a changelog entry

* Update the method docs

* Rearrange the default methods call order

* Revert formatting changes

* Move the clj-kondo ignore

* Update docs/developers-guide/driver-changelog.md

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

---------

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

* Add SNI check env var

* Update environment-variables.md

* Update docs/configuring-metabase/environment-variables.md

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

---------

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

* Add MB_ATTACHMENT_TABLE_ROW_LIMIT to docs

With default set to 20

* Update docs/configuring-metabase/environment-variables.md

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

* remove version

* range

---------

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

tested which is the min mysql version

* update minimum version for mysql

* format

@jeff-bruemmer pointed out that these names are redundant in #36723.

Theoretically one could argue that the settings aren't actually setting the "query row limit" - when you make a new
question, you can enter whatever limit you like. Instead, they're setting the *maximum* possible "query row limit."

That said, applying two limits is the same as applying the minimum of two limits, so calling it a "query row limit"
makes sense too, and might be more clear.