A suggestion to add an exception to help troubleshoot MongoDB projections.

[ru-ng]

I noticed that when events had the same name in the MapEvents() function, events just stops projecting to MongoDB. I spent quite a long time trying to pinpoint the problem and finally realised that our integration event name was the same as our domain event name and Eventuous wasn't sure which one it was referring to. I understand that it was our fault but it would be nice if Eventuous stopped with an exception instead of quietly running on. After renaming the integration event name, the MongoDB projections started to work.

[alexeyzimarev]

If you enable Eventuous logs, you will see log messages from different Eventuous components, including the type mapper. It logs a warning when event names are conflicting

eventuous/src/Extensions/src/Eventuous.Extensions.DependencyInjection/README.md

Line 13 in a66fb59

You can also add Eventuous logs to the logging provider by calling `app.AddEventuousLogs()`