Closes gh-15950

See gh-15950

Closes gh-15868

* pr/15943:
  Polish "Add a link to SpringMockK in the Kotlin documentation"
  Add a link to SpringMockK in the Kotlin documentation

Closes gh-15943

See gh-15943

This works around a change in javadoc generation in JDK 11.0.2. See
https://bugs.openjdk.java.net/browse/JDK-8212233 for details.

Fixes gh-15948

Closes gh-15825

This commit splits the management context configuration for jersey
into two separate configurations depending on if the type is SAME or
CHILD. The configuration for the SAME context should only kick in if
there is no existing ResourceConfig bean.

Fixes gh-15891

Closes gh-15867

Closes gh-15863

Closes gh-15813

Closes gh-15812

Closes gh-15869

Closes gh-15865

Closes gh-15864

Closes gh-15945

Closes gh-15946

Closes gh-15944

Closes gh-15901
Closes gh-15638

Closes gh-15862

Closes gh-15878

See gh-15775

Closes gh-15890

Closes gh-15348

When Spring Security is misconfigured it's possible to switch from an anonymous user
to a normal user. When switching back again, the corresponding
AuthenticationSwitchUserEvent will have a null target user. Previously, Actuator's
AuthenticationAuditListener would throw a NullPointerException when it received such an
event.

This commit updates the audit listener to defensively handled events with a null target
user.

Closes gh-15767

* pr/15859:
  Polish contribution
  Polish 'Database Initialization' section

Closes gh-15859

See gh-15859

* gh-15775:
  Polish "Use class for @ConditionalOnClass"
  Use class for @ConditionalOnClass

Closes gh-15775

See gh-15775

See gh-15775

This reverts commit 1f47bd97.

See gh-15915

Previously, the auto-configuration for both Jersey and WebMvc would auto-configure
a RequestContextFilter bean. In 2.1.0, this led to a startup failure due to the latter
attempting to override the bean defined by the former. In addition to the override there
were also problems with the order of the filter as Jersey uses -1 and MVC uses -105.

To avoid the above-described problems, the auto-configuration of the RequestContextFilter
was removed from JerseyAutoConfiguration in 2.1.1. Unfortunately, the broke
request-scoped beans for those using only Jersey.

This commit attempts to strike a better balance by reintroducing the auto-configuration
of RequestContextFilter in JerseyAutoConfiguration. It will back off if the user defines
their own filter or filter registration. WebMvcAutoConfiguration has been updated to
back off in the same manner. This leaves the potential for ordering problems, but they
are no worse than they were before. Furthermore, the user has the means to correct any
problems by using the various filter ordering properties that are provided for Jersey,
Spring Session, Spring Security, etc.

Closes gh-15376

This reverts commit 06feb728.

See gh-15914

* pr/15881:
  Polish "Document internationalization support"
  Document internationalization support