Create a new ApplicationPid class to remove the need for SystemUtils
and refactor existing calls.

... to wait for ApplicationContext to close in the 3 tests
that we needed to do so.

Fixes gh-664

Fixes gh-715

Fixes gh-709

Fixes gh-705

Fixes gh-700

This fixes a bug in the sample, where the AuthenticationManager it builds
is a local one for the filter chain containing "/login", whereas it was
expecting to override the Boot default, which is "global". The fix is
to extract the authentication configuration out into a
GlobalAuthenticationConfigurerAdapter.

Fixes gh-699

The docs related to YAML lists were out of date and
lacked an example making it clear how to bind to them.

See gh-501

If the user sets spring.mvc.locale and doesn't provide a @Bean
of type LocaleResolver then a FixedLocaleResolver will be provided.

Fixes gh-697, fixes gh-669

When mapping the ErrorController path to Spring Security it's
important that it starts with "/". This change ensures that is
the case even if the user has omitted the leading "/".

Fixes gh-694

This commit resolves #695 by changing the configuration so that all Java versions from 1.7 and above are allowed.

Fixes gh-693

Fixes gh-692

... it isn't: you have to set spring.datasource.platform

Partial fix for gh-337. See also gh-607 which complements this, but might
conflict on a merge.

User can now set up default properties in the Environment using
@IntegrationTest("foo:bar", "x:y") etc. Using "server.port:0" you
can get Tomcat or Jetty to spin up on a random port. We also add
a test listener that populates "local.server.port" with the actual
port the server started on so you can @Value("${local.server.port}")
inject it into the test case.

See gh-607 (this should make the extension of that PR to samples
much easier)

Otherwise Tomcat will go ahead and uncommit it and handle it again
in the ErrorReportValve (duh!)

Fixes gh-684

See gh-671

Prior to this commit, a dependency on a local file was not being
packaged by the Gradle plugin. This was a regression from the behaviour
in 0.5.0.M6 caused by the move to using a ResolvedConfiguration and
ResolvedArtifacts (4f677bec) to gain access to an artifact's type so
that non-jar artefacts could be filtered out. Since then, the approach
to filtering has been changed (38585bf3) and access to an artifact's
type is no longer needed.

This commit updates ProjectLibraries to restore its use of a
FileCollection rather than a ResolvedConfiguration when getting hold of
the files in a configuration. This means that the resulting jar will
now include dependencies that aren't resolved, such as those that are
provided as local files. The filtering that is applied to the files
is unaffected by this change and only files that are zip files will be
included.

Fixes #672

Fixes gh-513

User can specify the content type in external properties now, optionally
ommitting the charset (since that is duplicated). If charset is not
appended by user Spring will do it.

Fixes gh-671

Apparently yaml.org prefers .yaml, but the internet seems
to be more aligned with .yml, so I guess we should support both
out of the box.

Fixes gh-675

Fixes gh-673

Avoids loading a class if not needed, but doesn't seem to solve
any actual problems. I'll leave it in in case it helps later.

Testing gh-648

Fixes gh-646

Fixes gh-656