Closes gh-24080

Closes gh-24079

Closes gh-24078

Closes gh-24077

See gh-24034

Closes gh-24066

Closes gh-24060

Closes gh-24045

Closes gh-24058

This commit makes sure to use the most specific getter if more than
one candidate exists.

Closes gh-24002

Closes gh-23955

Closes gh-24055

See gh-24052

See gh-24041

Closes gh-24052

Fixes gh-24041

Closes gh-24046

A previous change intended to prevent temporary directories created as
an implementation detail of mounting volumes on kubernetes pods from
being used as a source for property files had a side-effect of also
preventing other types of hidden directories from being recognized. This
commit narrows the criteria for considering a directory as hidden,
using the kubernetes `..` prefix convention instead of the Unix `.`
prefix.

Fixes gh-23983

Closes gh-24039

See gh-24038

Closes gh-24038

Closes gh-24032

Closes gh-22974

Closes gh-24029

Closes gh-21121

Closes gh-24025

Closes gh-22908

Closes gh-24023

Previously, when an embedded test database was being auto-configured
any schema username and password specified by the user would result
in a separate embedded test database being created to load the schema.
This then left the actual test database without the schema causing
test failures.

This commit updates the test database auto-configuration to set the
schema username to an empty string in a property source that's added
first to the environment's property sources. This causes any schema
username configured by the user to be ignored, preventing the creation
of a separate database for schema.sql processing.

Fixes gh-19321

Closes gh-24021

* gh-24020:
  Fix typo in Spring Session documentation

Closes gh-24020

See gh-24020

Closes gh-24018

Closes gh-23151

Fixes gh-23821

* gh-23999:
  Polish "Avoid repeated calls of WebFlux and MVC registrations' getters"
  Avoid repeated calls of WebFlux and MVC registrations' getters

Closes gh-23999

See gh-23999

See gh-23999

Closes gh-24014

Previously, Quartz could be configured with a specific DataSource
using `@QuartzDataSource` but it was not possible to configure a
Quartz-specific transaction manager. This could result in the
different DataSources being used by Quartz itself and Quart'z
DataSourceTransactionManager.

This commit introduces a new qualifier, `@QuartzTransactionManager`,
that can be used to avoid the above-described problem. Any
`@QuartzTransactionManager`-annotated bean will be used by the
Quartz auto-configure configuration instead of the application's main
`TransactionManager`. If no such qualified bean is present, the
application's main TransactionManager, if any, will be used as before.

Fixes gh-20184