AXON-105 Fixed default queue-name configuration problem

The queue-name should not be configurable in the default-configuration element of a Terminal. The default queue name (as documented in the reference guide) is the name of the cluster it connects.
Replaced last references to Orange11 with Trifork
Added assertions to fail early on illegal null values

Issue #AXON-107 Fixed
Removed unused classes
Using constructor injection for event store in EventSourcingRepository

Instead of setter injection, the (mandatory) EventStore instance must be
configured using a constructor parameter.

Issue #AXON-108 Fixed
SagaRepository will not add Sagas if they are inactive

When a Saga was created and ended in the same invocation, the Repository would
erroneously store the saga. It would never be deleted. Now, the repository will
only store new saga instances if they return true on isActive().

Issue #AXON-109 Fixed
Support @SequenceNumber annotated parameters in a similar manner to @Timestamp
Added support for Publisher Acknowledgements in Spring AMQP Terminal

Publisher acknowledgements are a RabbitMQ specific feature that allows for
publishers to receive an ACK of each sent message, without the need for
transactions. Although there are less guarantees than with transactions the
performance is said to be 100x times better.

Issue #AXON-113 Fixed
Revised following review.

Mainly synthetic changes, apart from to add the support of primitive parameters as candidates for parameter resolution.
Update doc
Added support to explicitly configure payload type on @EventHandler

By explicitly adding the expected payload, handlers can remove the first
parameter in cases where only the Message or certain MetaData fields are
required.

Issue #AXON-62 Fixed
Merge remote-tracking branch 'markdingram/master'

Issue #AXON-114 Fixed
Improved test coverage for illegal state change detection

Added a test that checks for recognition of deleted aggregates where the
markDeleted is invoked in outside the EventHandler method.
Added logic to remove ParameterResolverFactories at runtime

This allows certain factories to only work within a limited scope of the
application's lifetime. This is especially useful when executing tests using
the test fixtures; resolvers should only be considered during the execution of
each specific fixture.

To ensure that cached handlers are invalidated, components that cache results
of ParameterResolverFactory should register a change listener. When a change is
detected, the cache must be cleared to ensure re-evaluation of all annotated
methods. It is unlikely to happen during Runtime, so the performance impact is
minimal.

Issue #AXON-100 Fixed
Preventing duplicate snapshots

Enhanced snapshotter to refrain from making a snapshot if only a single event
was needed to recreate the snapshot's state. This could result in duplicate key
violations in the Event Store.

Issue #AXON-120 Fixed
Fixed unit tests
fix AXON-121: detect usage of duplicate aggregateId
Minor modifications on previous commit
- Thrown exception should be ConflictingModificationException

Issue #AXON-121 Fixed
Added check to ensure provided Executor is suitable for AsyncSagaManager

The AsyncSagaManager checks whether the given executor actually starts the
requested processors. If they don't start within a specific timespan, an
exception is thrown. This detects the situation where the core pool size of a
thread pool is not large enough to accomodate all the processors.

Issue #AXON-125 Fixed
Added the CommandGateway as default resources in the Saga Test Fixture

The CommandGateway (or the mechanism that allows the creation of a gateway
using your own interface) is the recommended way to interact with a Command
Bus. Therefore, the CommandGateway is available as a default resource in the
test fixture.

Issue #AXON-112 Fixed