Upgrade to latest release of Spring AMQP and provide dependency
management for all of its modules

Closes #799

Closes #397 and #717

This commit provides several options to exclude one or more
dependencies:

* excludes allows to specify an arbitrary number of exclude sub
  element defining the groupId and artifactId of the dependency
  to exclude
* excludedGroupIds defines the comma separated list of groupIds
  to exclude
* excludeArtifactIds defines the comma separated list of artifactIds
  to exclude

While any artifact can be excluded, this is designed to exclude
provided-scoped dependencies that should not be bundled in the
executable jar/war.

The outcome of java -jar myapp.jar should be consistent with the run
goal: these exclusions are therefore applied to the classpath that
the run goal computes to launch the application.

This commit also adds some integration tests and updates the
plugin's documentation

Fixes gh-649, gh-650 and gh-674

Update documentation to use a real auto-configure class.

Fixes #791

fixes #587 and #588

fixes #791

Upgrade Boot to use Groovy 2.3.0 and provide dependency management
for all of Groovy's modules.

Closes #647

* module-version-mgt:
  Fixup reference guide following dependencies move
  Fixup POM harmonization
  Harmonized maven dependency management

Update reference guide to indicate that spring-boot-dependencies should
be imported when not using the parent POM.

Fix POM harmonization so that the release process now
prepares the dependencies POM rather than starter-parent

This commit harmonizes the dependency management of internal modules
so that versions can be omitted everywhere. Update the maven coordinates
to provide the full groupId for consistency

Freemarker integration tests now use a random port so boot
builds properly when port 8080 is taken.

Update the reference guide to add a call-out to the new generated
maven plugin site.

Finishes gh-772

* pull780:
  Add multi-datasource health indicator support
  Add CompositeHealthIndicator

Update EndpointAutoConfiguration to support multiple datasources.

Fixes gh-783

Add CompositeHealthIndicator that allows multiple HealthIndicators
to be combined into a single result.

Fixes gh-782

* docfix:
  Minor documentation fixes

Fixes gh-781

Previous to this commit, the remote shell security configuration
described that a default password will be generated with no extra
configuration. Actually, when Spring Security is configured for the
application, the remote shell reuses that configuration by default.

It turns out that the default log message is confusing as it was
referring to "application endpoints". Updated that log to a more
generic log message and updated doc accordingly.

Fixes gh-779

Fixes gh-778, Fixes gh-755

Fixes gh-776

Add previously implicit <groupId>org.apache.maven.plugins</groupId>
to plugin declarations.

Add spring-boot-docs to the default profile so that imports by default
into eclipse.

Remove the filtering from test jars so Maven works in the same way
as eclipse. Test jar filtering has now been setup on the CI server
to prevent them from being published.

Fixes gh-754

Commit e26e06d5 broke the full build as the generated zip file for
the size is not generated. Actually, the site plugin has a jar goal that
is exactly meant for what we need to do.

This commit removes the use of the assembly plugin and invokes the
jar goal of the site plugin when the full profile is enabled.

Relates to #749

Extract into a utility to be shared between Shell and RunMojo

Fixes gh-773

This commit adds the generated site for the maven plugin alongside
the developer guide and javadoc. The maven plugin is available in
the "/maven-plugin" context.

The advanced information described in the developer guide have
been migrated to the plugin site as most the information is taken
from the code itself, which avoids duplication.

Fixes #749

Fixes gh-759

Fixes gh-771

The problem all along has been in AsciiBytes, so the fix in
commit ce3aaf was just a stop gap for a system where multi-byte
characters are supported but the default encoding is not UTF-8 (e.g.
most Windows systems). The real solution is not to leave it to
chance and always pick an encoding for the JarEntry names (i.e.
in AsciiBytes).

Fixes gh-764

They only add a single extra dependency, so not really
much value.

Fixes gh-770

Restore `freemarker.template.Configuration` bean for the
FreeMarkerWebConfiguration. The @Bean method no longer uses a
@Condition since `FreeMarkerConfig` must already exist.