See gh-22125

See gh-22125

* gh-22120:
  Upgrade to Flyway 6.5.0 and support createSchemas

Closes gh-22120

See gh-22120

Closes gh-22136

Closes gh-22135

Closes gh-22134

Closes gh-22133

Closes gh-22132

Closes gh-22131

Closes gh-22130

Closes gh-22129

Closes gh-22127

Closes gh-22126

See gh-21932

Closes gh-21931

Closes gh-22121

This commit improves the validation performed on the user
input provided to the layertools jarmode to provide more
clear error messages when the input is not correct and
reduce the chance of ambiguity.

Fixes gh-22042

* gh-221144:
  Update Atmosphere versions used in smoke test

Closes gh-221144

See gh-221144

Closes gh-22078

Closes gh-22106

Closes gh-22099

* gh-22093:
  Polish "Disable XML reader when spring.xml.ignore is true"
  Disable XML reader when spring.xml.ignore is true

Closes gh-22093

See gh-22093

This commit allows to set the XmlBeanDefinitionReader field from
BeanDefinitionLoader to null in a way that allows the GraalVM native
compiler to remove it from the native image when the spring.xml.ignore
flag introduced by spring-projects/spring-framework#25151
is set to true.

The purpose of this change is to allow smaller footprint on native
images without requiring to use GraalVM native substitutions
which are unmaintainable by nature and also to increase the consistency
between JVM and native images.

In order to effective, this optimization requires BeanDefinitionLoader
class to be initialized at build time.

See gh-22093

See gh-22105

Closes gh-21930

Closes gh-21929

Closes gh-21927

Closes gh-22105

Closes gh-22103

Closes gh-22102

Previously, the thread dump endpoint's response could exceed
WebClient's in-memory buffer limt when there were a large number of
threads or the threads had large stacks.

This commit disables WebClient's in-memory buffer size limit so that
the test passing is not dependent on the number of active threads and
their stack sizes.

Closes gh-22101

This commit changes the information provided by
RedisReactiveHealthIndicator to include cluster details when Spring
Data Redis detects that Redis is running in a clustered configuration.
This brings the reactive and non-reactive Redis health indicators
into alignment.

Fixes gh-21514

Closes gh-22095

Fixes gh-22061 in 2.3.2

Prior to Spring Data Redis version 2.2.8, the contents of the
Properties object returned from the
ReactiveRedisConnection.ServerCommands.info API were the same
for clustered and non-clustered Redis configurations, containing a set
of key/value pairs. This allowed ReactiveRedisHealthIndicator to get
a version property using a well-known key. Starting with Spring Data
Redis 2.2.8, the info property keys contain a host:port prefix in a
clustered Redis configuration. This prevented
ReactiveRedisHealthIndicator from getting the version property as
before and resulted in the health always being reported as DOWN.

This commit adjusts ReactiveRedisHealthIndicator to detect the
clustered configuration from Spring Data Redis and find the version
property for one of the reported cluster nodes.

Fixes gh-22061

See gh-21928

See gh-21932