Expanding message registration exception message as it is a little misleading

The exception message states that the messages must implement, IMessage, IEvent or ICommand however this may not have been the cause of the exception. If the user has configured NSB such that the message types have never been registered (e.g. NSB has not scanned the required assembly) then they will also get this error message even though their messages implement the correct interfaces.
messing with a behavior pipeline or a chain or a Russian doll or whatever
small adjustments
Modified the spike to show how a user can build a UoW and how it would
lean on the child container to pass the session. For other internal
behaviours I'd say we should use the context.Set() instead. I also think
we need a Get|Set(string) since we need to add eg the message and saga
data and we need to get access to it without knowing the type
Merge branch 'develop' into sagapipeline
added impersonation behavior
remove static dep on builder instance and make behavior chain use child builder
added generic behavior that can be used while 'porting' behaviors
configured pipeline to be close to 'the real deal'
doesn't really pass the tests yet
made test pass
moved some more logic into behavior
messing with a behavior pipeline or a chain or a Russian doll or whatever
small adjustments
Modified the spike to show how a user can build a UoW and how it would
lean on the child container to pass the session. For other internal
behaviours I'd say we should use the context.Set() instead. I also think
we need a Get|Set(string) since we need to add eg the message and saga
data and we need to get access to it without knowing the type
added impersonation behavior
remove static dep on builder instance and make behavior chain use child builder
added generic behavior that can be used while 'porting' behaviors
configured pipeline to be close to 'the real deal'
doesn't really pass the tests yet