* gh-15822:
  Polish "Set NO_REQUEST_TIMEOUT as a server option not a socket option"
  Set NO_REQUEST_TIMEOUT as a server option not a socket option

See gh-15822

See gh-15822

* gh-15889:
  Do not auto-configure OEMIV filter when user defines registration bean

Closes gh-15889

See gh-15889

* gh-15876:
  Polish "Remove unwanted @Nullable annotations"
  Remove unwanted @Nullable annotations

Closes gh-15876

See gh-15876

See gh-15876

Closes gh-15892

* gh-15791:
  Polish "Test the Gradle plugin against Gradle 4.10.3 and 5.1.1"
  Test the Gradle plugin against Gradle 4.10.3 and 5.1.1

Closes gh-15791

See gh-15791

This commit also ensures that Jersey-based actuator endpoints are
available before the user has configured a `ResourceConfig` bean

Fixes gh-15625
Fixes gh-15877

See gh-15878

Prior to this commit, the `HttpTraceWebFilter` would collect the
response information (status and headers) for tracing purposes, after
the handling chain is done with the exchange - inside a
`doAfterSuccessOrError`.

Once the handler has processed the exchange, there is no strong
guarantee about the HTTP resources being still present. Depending on the
web server implementation, HTTP resources (including HTTP header maps)
might be recycled, because pooled in the first place.

This commit moves the collection and processing of the HTTP trace right
before the response is committed. This removes the need to handle
special cases with exceptions, since by that time all exception handlers
have processed the response and the information that we extract is the
information that's about to be written to the network.

Fixes gh-15819

Prior to this commit, errors unhandled by custom `WebExceptionHandler`
and resulting in an HTTP 500 status would not be logged at ERROR level,
giving no information to developers about the actual exception.

This commit ensures that such exceptions are logged at the ERROR level
with their exception. By the time the exception hits the
`DefaultErrorWebExceptionHandler`, if the response is already committed
or if the exception is due to a client disconnecting, the error is
delegated to Framework support as Spring Boot won't be able to render an
error page as expected.

Fixes gh-15769

* pr/15873:
  Polish

Closes gh-15873

* pr/15871:
  Fix assertion

Closes gh-15871

Fixes gh-15790

See gh-15869

See gh-15868

See gh-15867

See gh-15866

See gh-15865

See gh-15864

See gh-15863

See gh-15862

Closes gh-15847

Closes gh-15815

Closes gh-15843

Closes gh-15844

Closes gh-15761

Closes gh-15810

* pr/15798:
  Polish "Inject Map directly rather than via ObjectProvider"
  Inject Map directly rather than via ObjectProvider

Closes gh-15798

See gh-15798

* pr/15778:
  Polish "Handle AccessControlException in JspTemplateAvailabilityProvider"
  Handle AccessControlException in JspTemplateAvailabilityProvider