Issue: SPR-14140

(cherry picked from commit aa5c12c5)

`@InitBinder` annotated methods are not meant to be part of the public
contract of Controller and should be package protected.

Issue: SPR-14135

This commit introduces a new method in TestPropertySourceUtils that
allows properties files to be added directly to the environment without
the need for a ConfigurableApplicationContext upfront; however, a
ResourceLoader is still necessary.

Issue: SPR-14131

Issue: SPR-14121

Issue: SPR-14121

Issue: SPR-12402

Issue: SPR-14128

BeanDefinitionBuilder keeps providing addConstructorArg(Object) for Spring Security 2.x compatibility

Issue: SPR-14123

Issue: SPR-8055

DefaultListableBeanFactory leniently deserializes into dummy factory if serialization id not resolvable

Issue: SPR-14117

Issue: SPR-13706

Issue: SPR-14116

Latest dependency updates (Caffeine 2.2.6, EhCache 3.0 RC2, Joda-Time 2.9.3, Netty 4.0.36, Rome 1.6, SLF4J 1.7.21, Tomcat 8.0.33, Undertow 1.3.20, Woodstox 5.0.2, JOpt-Simple 5.0)

Previous refactoring (fcf6ae and also 43d937) in the SockJsSession
hierarchy consolidated access to the request and response in the
base class AbstractHttpSockJsSession in order to keep synchronization
concerns there. However that also unintentionally removed the call to
resetRequest() after sending a heartbeat for any of the
PollingSockJsSession classes. In general a polling session should call
resetRequest after every frame written.

This commit brings back the writeFrame override in PollingSockJsSession
with an extra call to resetRequest().

Issue: SPR-14107

Prior to this commit, the size of the ApplicationContext cache in the
Spring TestContext Framework could grow without bound, leading to
issues with memory and performance in large test suites.

This commit addresses this issue by introducing support for setting the
maximum cache size via a JVM system property or Spring property called
"spring.test.context.cache.maxSize". If no such property is set, a
default value of 32 will be used.

Furthermore, the DefaultContextCache has been refactored to use a
synchronized LRU cache internally instead of a ConcurrentHashMap. The
LRU cache is a simple bounded cache with a "least recently used" (LRU)
eviction policy.

Issue: SPR-8055

Commit 48236b from 2014 introduced a logging improvement to avoid
logging each removed session per line and instead log one line at
the end with all removed sessions ids. However that list of removed
session ids wasn't populated. This commit fixes that.

Issue: SPR-14111

Ignore container's auto-startup once the context is refreshed.

Issue: SPR-14015

* pr/1027:
  Fix typo

Closes gh-1027

Issue: SPR-14108

Issue: SPR-14097

Issue: SPR-14110

Issue: SPR-14109