No longer build hamcrest-all.

There's no need for hamcrest-all when using a
dependency manager; omit it.
Copy the existing release poms into place.

- Start with the existing release poms; copy them into place so they
   can be used to build with.
- Ignore the Maven build's working directory.
Specify the current version in the build poms.

Specify the current version and declare a source encoding so these
poms can be used directly to build.
Fold hamcrest-api into hamcrest-core to match distribution.

Hamcrest-api is already folded into hamcrest-core during release.
Move the classes so it's like that at build time as well.
Include necessary build and test dependencies in the poms.

- Include the dependencies to build and test hamcrest-core,
   hamcrest-generator and hamcrest-library.
- As well as the test dependencies, copy over AbstractMatcherTest.java
   to avoid introducing a new test-utilities module.
- Since 4.11, junit doesn't bundle any dependencies, so use
   it instead of junit-dep.
Create CoreMatchers in the generate-sources phase.

Create CoreMatchers.java in generate-sources, then include it
in the build.
Copy the config from CoreMatchers across to Matchers.

Copy across the configuration so that Matchers is built in the same way
as CoreMatchers.
Fix building and running the examples as tests.

- Add a pom for hamcrest-examples.
- Include TestNG as a dependency.
- Fix a failure-demonstrating test to not fail the build.
- Specify that the examples should be run as tests.
Merge branch 'build-with-maven' of https://github.com/josephw/JavaHamcrest
Point SCM info to Atlassian's fork for a release.
Set distribution management to deploy to Atlassian's 3rd party repo.