This reverts commit 66fba938.

See gh-16910

Closes gh-16926

Closes gh-16925

See gh-16909

Closes gh-16913

Closes gh-16912

Closes gh-16911

Closes gh-16910

* pr/16756:
  Polish 'Drop blocking RedisReactiveHealthIndicator calls'
  Drop blocking RedisReactiveHealthIndicator calls

See gh-16756

Update `RedisReactiveHealthIndicator` so that `getReactiveConnection`
is not called directly since it blocks.

Fixed gh-16756

Update `JavaBeanBinder` so that overloaded setters can be used when
binding. Prior to this commit the setter picked would depend on the
order that the JVM returned the declared methods. We now consistently
prefer using the setter with a parameter type that matches the getter.

Closes gh-16206

Update the auto-configured Jetty `HttpClient` so that a default
`SslContextFactory` is used.

Prior to this commit connecting to https URLs would cause a
`NullPointerException`.

Fixed gh-16810

Update `JavaBeanBinder` so that previously cached beans are compared
using full generic type information. Prior to this commit binding would
fail if a class with the same resolved type, but different generics was
in the cache.

Fixes gh-16821

Update the promote and sync jobs so that only the build-info.json
file is downloaded.

Closes gh-16448

Closes gh-16842

Closes gh-16841

Closes gh-16840

Closes gh-16839

Closes gh-16838

Closes gh-16837

Closes gh-16724

Closes gh-16749

Closes gh-16751

Closes gh-16753

Closes gh-16836

Closes gh-16748

This commit restores the read-only `finalName` so that its value can
be lazily resolved against `${project.build.finalName}`.

While doing the evaluation ourselves and not relying on a dedicated
field at all would have been better, the evaluation increased the
number of required dependencies for no good reason.

IDEs should not offer auto-completion for that read-only field and it
is not published in the generated site either.

Closes gh-16456

* pr/16730:
  Fix 'spring.resources.cache.period' for WebMvc

Before this change it got overwritten by forwarding an empty
CacheControl to Spring. Spring itself sets CacheSeconds already
correctly in absence (=null) of a CacheControl.

Also:
* Fixes bug in WebMvcAutoConfigurationTests.cachePeriod which
prevented it to assert anything

See gh-16488
Closes gh-16730