In 2.2.0, @ConfigurationPropertiesScan was enabled by default.
Unfortunately, this had the unexpected side-effect of breaking
conditional enablement of a @ConfigurationProperties class via
@EnableConfigurationProperties if the @ConfigurationProperties class
was in a package covered by scanning.

This commit remove @ConfigurationPropertiesScan from
@SpringBootApplication so that it is no longer enabled by default.
2.1.x users who rely upon such conditional enablement of
@ConfigurationProperties classes can now upgrade to 2.2.x without
having to make any changes. Users who do not have such a need and are
in a position to use configuration properties scanning can now opt-in
by adding @ConfigurationPropertiesScan to their main application class
alongside @SpringBootApplication.

Closes gh-18674

Closes gh-18743

Previously, all of the type exclude filters in
spring-boot-test-autoconfigure were package-private. This prevent a
user who was creating their own test slice from composing their own
TypeExcludeFilter with one of Boot's.

This commit updates all of the TypeExcludeFilters in the
test-autoconfigure module to make them public. The intention is only
to allow them to be composed with other type exclude filters when
referenced in a @TypeExcludeFilters annotation. Therefore, each
filter class is declared final and their constructors remain
package-private.

Closes gh-18746

* pr/18847:
  Add missing reference to HazelcastHealthContributorAutoConfiguration

Closes gh-18847

See gh-18847

Closes gh-18851

* pr/18848:
  Drop JDK 12-based CI

Closes gh-18848

See gh-18848

Closes gh-18850

* pr/18845:
  Test the Gradle Plugin against Gradle 5.6.4

Closes gh-18845

See gh-18845

Closes gh-18733

Closes gh-18737

Closes gh-18840

Closes gh-17261

Closes gh-18798

* pr/18837:
  Add reference to Armeria starter

Closes gh-18837

See gh-18837

* pr/18838:
  Polish

Closes gh-18838

See gh-18838

* pr/18833:
  Remove unnecessary log4j exclusion

Closes gh-18833

See gh-18833

This commit creates a new configuration property
`spring.codec.max-in-memory-size` which configures the maximum
amount of data to be buffered in memory by codecs (both client and
server).

This property has no default value - it will let Spring Framework handle
the default behavior, currently enforcing a 256KB for provided codecs.

Fixes gh-18828

Closes gh-18818

Closes gh-18824

Closes gh-18823

Closes gh-18822

Closes gh-18821

Closes gh-18820

Update `HealthEndpointConfiguration` to also include adapted reactive
health contributors when project reactor is on the classpath. Prior to
this commit, reactive contributors were only exposed in WebFlux
applications. This was a regression from Spring Boot 2.1 that we didn't
catch because all our own reactive contributors all have non-reactive
equivalents.

Closes gh-18805

This commit is a follow-up of a change in Spring Framework[1] to make
sure injection points that are expecting a specific bean by name use
a qualifier.

As a result of this change, MVC uses the dedicated MVC validator again
rather than the general one auto-configured by Spring Boot.

[1] https://github.com/spring-projects/spring-framework/issues/23887

Closes gh-18672

Closes gh-18802

Closes gh-18801

Closes gh-18800

Closes gh-18799

Closes gh-18797

Closes gh-18796