Feature/outboundheaders change

Removed the hard dependency on the UserInfoRepository and made it an optional dependency.  Currently the only UserInfoRepository implementations are Kerberos based.  This allows a little more flexibility and simplifies the configuration if you really have no need for it.  Currently in our project the Sender Identity is always being set to the user that initiated the sequence of events and is propagated to all levels there for not requiring a UserInfoRepository.  I also believe the current implementations of UserInfoRepository assumes that the services are running as accounts hooked into a AD Domain which is also not our case.