Refactoring the Public API

[tdashworth]

This library is flexible and powerful although, in my opinion, it lacks a friendly API to use it. Additionally, this repo houses a number of projects although only the XRM engine is released as a public NuGet package.

I propose a few things for us to discuss:

1. splitting the repo or reorganising it to separate the generic engine and XRM implementation
2. publicly releasing the generic library via NuGet so that others can use it (e.g. SQL and SharePoint)
3. evaluate the public API of these libraries so they are more intuitive to use - maybe explore a fluent style or builder API since most of the effort is in configuration the source, target, and processors.

I don't imagine this being a quick turn around but if we can at least formulate a plan, we can break that up into manageable issues.

[tdashworth]

@ksulikow @realekhor @markcunninghamuk @ewingjm I have opened this GitHub Discussion as this is too big to be considered an issue. Let's use this as a forum to plan our end goal.