* pr/7522:
  Fix broken doc formatting

Closes gh-7522

Closes gh-6496

* pr/7491:
  Polish contribution
  Detect default values defined in the parent

Closes gh-7491

Closes gh-5434

This commit adds `@JdbcTest`, a new test slice for pure jdbc tests. It
provides the same basic features than `@DataJpaTest`.

Closes gh-6563

Closes gh-7433

* pr/7510:
  Remove redundant toString() invocation

Closes gh-7510

* gh-7263-2:
  Add custom LayoutFactory sample
  Support custom fat jar layouts
  Rework Repacakger timeout code

Add a sample that shows how a custom LayoutFactory can be used with
both Maven and Gradle.

Closes gh-7263

Allow support for custom Lyout implementations with both the Maven
and Gradle plugin. Implementations of `LayoutFactory` can now be
specified to allow customization of the layout. In addition a
layout may now implement `CustomLoaderLayout` if it wishes to
write custom loader classes.

See gh-7263

Pull up common timeout code into Repackager and remove the need for
custom subclasses.

See gh-7263

Closes gh-6763

Checking for the presence of a `ValidationProvider` resource is
unfortunately not enough to trigger the validation auto-configuration.

If `hibernate-validator` is added on the classpath without a `javax.el`
implementation, the former will blow up on startup. So far this was a
pilot error so we didn't have to care about it. Now that we have an
auto-configuration that may lead to this error, we need to be extra
careful and check that scenario ourselves.

This commit adds an extra condition that runs as late as possible and
attempt to actually initialize a `Validator`. If that fails for whatever
reason, the auto-configuration will now back off.

Several additional tests have been added to exercise this scenario.

Closes gh-6228

Closes gh-7496

Closes gh-7489

See gh-6995

* pr/7494:
  Add ValidationAutoConfiguration to spring.factories

Closes gh-7494

Closes gh-7485

* gh-7271:
  Test that a broken factory bean does not break resetting of mocks
  Prevent a broken factory bean from breaking the resetting of mocks

Previously, ResetMocksTestExecutionListener used getBean(name) to
retrieve each instantiated singleton. When the instantiated singleton
was a factory bean, this would cause getObject on the factory bean to
be called. If the factory bean was unable to produce its object, for
example due to test slicing excluding something, an exception would
be thrown.

The previous commit updated ResetMocksTestsExecutionListener to
use getSingleton(name) rather than getBean(name).  This will retrieve
the factory bean itself rather than causing the factory bean to
attempt to create an object. This commit updates the tests to verify
the new behaviour.

Closes gh-7270

Closes gh-7271

* gh-7175:
  Document and test array support for spring.profiles.*
  Use data binding to access spring.profiles .active and .include

Closes gh-7175
Closes gh-6995