Closes gh-8050

* pr/8057:
  Fix entry in broken-initialization.factories

Closes gh-8057

Closes gh-8055

Previously, AspectJ would find META-INF/aop.xml almost as soon as
the jar was launched, and before LaunchedURLClassLoader had been
created. This meant that AspectJ would attempt to load aspects listed
in META-INF/aop.xml but that were package in BOOT-INF/classes and,
therefore, could not be loaded.

This commit updates the Repackager so that a META-INF/aop.xml file
is moved into BOOT-INF/classes. This ensures that it isn't visible
to the app class loader so it won't be loaded to early. It will
now be loaded by LaunchedURLClassLoader which can also load the
compiled aspects that aop.xml references.

Closes gh-7587

Closes gh-7360

Closes gh-8000

Closes gh-7360

Closes gh-2753

* pr/8047:
  Upgrade to Spring LDAP 2.3.0.RELEASE

Closes gh-8047

* pr/7600:
  Polish contribution
  Add slide test annotation for MongoDB

Closes gh-7600

This commits adds a slice test infrastructure for MongoDB, similar to
what `@DataJpaTest` does with JPA.

By default, an embedded Mongod process is used if available.

See gh-7600

This commit improves the logic of the embedded Mongo support to use a
random port if no custom port has been specified. This doesn't change
the default if the embedded support isn't active.

Closes gh-8044

Previously, the actuator's endpoints produced application/json and,
where appropriate, also consumed application/json. Without a custom,
versioned media type, it's impossible for us to make changes to the
endpoints without breaking clients.

This commit introduces a new media type,
application/spring-boot.actuator.v1+json, that is now produced by
default with application/json also being produced if requested.
Endpoints that consume JSON will now also accept content the uses
the new media type in addition to application/json.

Closes gh-7967

* pr/8039:
  Indenting SpringApplication javadoc code

Closes gh-8039

Closes gh-8040

* pr/8038:
  Upgrade to Spring AMQP 1.7.0.RELEASE

Closes gh-8038

Closes gh-8033

Closes gh-7974

Fixes gh-7091

Closes gh-7862

Previously, when the ExpectedException JUnit rule was used with
FilteredClassPathRunner a LinkageError would occur if any of
ExpectedException's methods that take a Hamcrest Matcher were called.
This was due to the FilteredClassLoader delegating loading of
org.junit classes to its parent but not org.hamcrest classes. This
resulted in JUnit classes loading one version of the Hamcrest class
and the test class loading another.

This commit ensures that both the JUnit classes and the test class
use the same version of Hamcrest classes by also delegating the
loading of org.hamcrest classes to FilteredClassLoader's parent.

* pr/8030:
  Fix closing parentheses

Closes gh-8030