Changes to the DomainEventCatalog, added a sample project for automatic Query Model rebuilding

Changed the domainevent catalogs they now return a class containing
detailed information about where the event handles is located and not
only the function to invoke.
Added a sample project to handle automatic Query Model rebuilding at the
engine startup if any of the denormalizers change over time
removed unneeded files, added missing
Merge branch 'master' of https://github.com/andreabalducci/Prxm.Cqrs

Merge with master
docs
Added a project for Sagas and some possible infrastructure files
Some modifications to the concept, nothing working yet
Adding the same Invoker structure to Commanding/ICommandHandlerCatalog.cs
Intercepted commit of EventStore to save each event in a MONGO db to use for replay.
Created a Sample.Server.Core.csproj to contain all helper classes that could be subsequently moved to the main core infrastructure.

Created the concept of Initializers of DomainEvent Handlers, this is quite ugly because actually it is initializated in Program.cs of sample.server, but the code should be moved to the handler catalog.

Used this initiqalization concepts in NHDenormalizer to reinitialize the QueryModel NHibernate based on version number of the denormalizer.
Fixed nhdenormalizers. Added nhprofiler
changed a little bit the PersistedDomainEvent.cs to include more information on commit id and stream id.
fixed namespace, inserted command executor stora
Persisting of commands with castle interceptor. Mainly created to evaluate the strategy of using interceptor to automatically capture some information about core pipeline without the need to modify or insert class in core.
Marked an old command as obsolete.
fixed a little bit the wpf sample project, now it is full MVVM
skeleton for a smar console monitoring based on log4net
added minimal infrastructure to incercept log4netlogger to create a wpf console to debug infrastructure
inserted a minimal project to manage logview.
First rudimental implementation of logger viewer.
added support for optype in logging

This functionality is useful to group logs togheter and to build a ui
that is capable of showing aggregate logs based on logical operations
executed by the system.