Add a RequestPreprocessor SPI to support path mappings in distribution messages

We have a use case where the target system of Sling Content Distribution has a different content structure / path names than the origin system. 

To support this we would like to propose the addition of a RequestPreprocessor SPI that allows us to apply a path mapping to the objects contained in a distribution messages. 

This SPI should be used in the journal based distribution implementation.