Reducing of thight coupeling between components

The undoRedoHandler, saveAndLoadHandler and the objects themself combine to much functionality right no, even out of their scope (e.g. the inspectorComponents inside the objects).

This tight coupeling should be reduced, for example:
- split up the saveAndLoadHandler for each type of object + easier way to adapt to changes
- Consider the objects as a kind if model only holding data and only basic functionality.
- Consider handeling undo redo functionality by default (e.g Proxy for getter and setter)

Start by tracing the undoRedoHandler, saveAndLoadHandler, and the objects that currently contain inspectorComponents and other functionality. Document which responsibilities are outside each component's scope before deciding how to separate persistence, model data, and undo/redo behavior. Done means the proposed responsibility boundaries are clear and the handlers can be adapted without coupling to unrelated object functionality.

Written by the indexing model from the issue text.