Move RequestReplyHeaderMapper to spring-messaging

This commit moves the RequestReplyHeaderMapper and related base
implementation from Spring Integration to the core messaging module.

AbstractHeaderMapper has been changed from its original version in
a number of ways:

* The 'userDefinedHeaderPrefix' property has been removed as some
  advanced tests revealed that the feature is actually broken right
  now and there is no easy way to fix it. It can be restored at any
  time in SI with a richer hook point that indicates if the property
  comes from the target object or the standard MessageHeaders.
* A HeaderMatcher interface has been introduced to replace the
  lengthy checks in shouldMapHeader. Several implementations
  of that interface are provided
* An additional pattern has been added that maps any header that is
  *not* a standard header. It uses the standardHeaderPrefix property
  for that purpose
* The default mapping behaviour has changed. Standard request/reply
  headers are mapped as well as all non standard headers: this
  basically means that custom headers are now mapped by default. This
  new default can be easily changed by overriding the
  'createDefaultHeaderMatcher' method
* A number of protected method that were only used to create the
  instance have been removed in favour of a non default constructor.
  Subclasses should provide those *static* values in their own default
  constructor.
* The list of transient headers can now be customized. Transient
  headers are headers that should never be mapped. The standard
  ErrorChannel and ReplyChannel headers have also been removed from
  the default transient headers list as they no longer need to be
  transient

Issue: SPR-12072