Issue: SPR-16611

Issue: SPR-16607

* Fix AsciiDoc typos in AOP documentation

* Polish formatting

Issue: SPR-16606

Issue: SPR-16601

Issue: SPR-16602

The former method clashed with the ClientRequest.method() getter.

This commit introduces ClientResponse.Builder, an easier way to create a
ClientResponse from an existing response, or from scratch.

Issue: SPR-16553

Issue: SPR-16599

Issue: SPR-16591

Issue: SPR-16597

Issue: SPR-14694

Issue: SPR-16488

Support @ResponseStatus annotated exceptions.
Supported root cause exceptions with response status information.

Issue: SPR-16567

Issue: SPR-16588

Issue: SPR-16592

Issue: SPR-16584

This commit allows several DeferredImportSelector instances to be
grouped and managed in a centralized fashion. This typically allows
different instances to provide a consistent ordered set of imports to
apply.

Issue: SPR-16589

This commit picks up where SPR-14498 left off by adding support for an
explicit target type when using JsonPath to perform an assertion against
the response content using a Hamcrest Matcher.

Specifically, there is a new overloaded value(Matcher<T>, Class<T>)
method in JsonPathResultMatchers for use with Hamcrest matchers where
the target type (i.e., Class<T>) can be specified.

Issue: SPR-16587

Support asserting JSON regardless of order and formatting.
Based on same JsonExpectationHelper used in ContentResultMatchers.

Issue: SPR-13919

With this change the code generation for method and property
references is modified to include branching logic in the
case of null safe dereferencing (?.). This is complicated
by the possible usage of primitives on the left hand side
of the dereference. To cope with this case primitives are
promoted to boxed types when this situation occurs enabling
null to be passed as a possible result.

Issue: SPR-16489

Issue: SPR-16582

Issue: SPR-16581

Notice that per specification, only Unicode is supported
(UTF8, UTF16_BE, UTF16_LE, UTF32_BE, UTF32_LE).

Issue: SPR-16539

Issue: SPR-16564

Issue: SPR-16564

Issue: SPR-16577