Remove dual source MAP layer from XTS and rely on JBossWS implementation

The fix to JBTM-265 defined its own MAP (message addressing properties) abstraction layer to hide details of the two different JBossWS-Native/CXF AddressingProperties implementations. The MAP code was implemented in dual source versions for either Native or CXF. JBossWS 3.2.0 introduced an implementation of this MAP abstraction layer in the underlying WS stacks. So, XTS needs to discard its own implementation and use whatever version it finds in theinstalled JBossWS libraries. This effectively reduces the XTS implementation to single source once again.