Merged SetupProvider into ProcessEngine

[dbeuchler]

The module SetupProvider was integrated into the ProcessEngine for many reasons:

• The SetupProvider was a optional dependency of the ProcessEngine but it cannot be meaningfully deployed without the ProcessEngine, the separation is a leaky abstraction.
  Merging removes indirection (extra DI registrations, configuration, assembly loading, error handling paths) and simplifies the overall model.
• High coupling with low autonomy is a signal that the components belong together
• Fewer NuGet references, less transitive dependency bloat, fewer binding redirects
• Preconditions that the SetupProvider should be present for all features of the ProcessEngine can be enforced as internal invariants rather than scattered runtime checks.

Upgrade hint: Move SetupTriggers config-section from the Moryx.ControlSystem.SetupProvider.ModuleConfig.json to Moryx.ControlSystem.ProcessEngine.ModuleConfig.json