Summary

This PR fixes the wrong state caused by swapping specs props between existing components.

The root cause is the specComponentFactory.
The issue appears in the following situation:

• we have two components with respective ids A and B
• this got parsed and stored in our state
• the consumer switch the ids of the two components: the first component (previously with id A) becomes the one with id B and the second component (previously with id B) becomes A.

Because we are processing these specs sequentially following the React life cycle, the first component calls the following part of the specComponentFactory

if (prevId && prevId !== props.id) {
    removeSpec(prevId);
}
upsertSpec(SpecInstance);

this removes the prevId spec (the A for the first component) and then add the spec B to the store (1).
Then it's time for the second component. The id of the component has changed so it follows the same path as the previous one: removes the spec B (its saved previous id) and then upsert the spec with id A, but the removed spec B is not the old one, but a new one added in the step (1), the new one provided by the first component.

The first time we send anupsertSpec action to the state, the reducer cleans up the specs array. Because of this, it is not needed to call first the removeSpec with the prevId, if that is different from the current one. We still clean and re-add all the specs on upserting.

fix #868

Checklist

• Unit tests were updated or added to match the most common scenarios