Save component properties must not set the initial render state

When component properties are saved the component is redrawn in it's initial render state. There is no need for that, since after 'on properties changed' the component is already redrawn. The state that is saved is already shown.

Further more: when working with a component with multiple variants (using Relevance), when you changed configurations of another variant than the original, it is a bug that the initial state is rendered! The component properties tab shows the properties of tab 2, but the component is rendered with the state of the default tab.

Even more further: when a component has head contributions, and the component is rendered twice when using "save & close", angular gives a warning that the app is loaded twice. See screenshot for the browser console warning.