RSA-RTE: State machine of derived capsule damaged when adding abstraction

This RFE is related to the mentioned PMR. The PMR will result in a warning that helps avoiding damaging the state machine.

The RFE is entered to really fix this issue.

---

I have 3 capsules:
- A_AbstractCapsule
- A_IntermediateCapsule (derived from A_AbstractCapsule)
- A_DerivedCapsule (derived from A_IntermediateCapsule)

All have state behavior, operations and attributes, added on top of its abstract capsule.

I decide to add an extra abstraction between A_IntermediateCapsule and A_DerivedCapsule, named A_ExtraIntermediateCapsule.

This is what I do:
- Add new capsule A_ExtraIntermediateCapsule.
- Derive it from A_IntermediateCapsule.
- Pickup the generatization arrow and move it from A_IntermediateCapsule to A_ExtraIntermediateCapsule.

Then I open A_DerivedCapsule and the state behaviour seems to be damaged. My top state is still there, but it's empty now. The top state of the abstract class is visible next to the existing one.

I've seen this behaviour in my project model with:
- RSARTE 9.1.2 patch 46
- RSARTE 10

I tried to reproduce it on a colleague's system. Same result.
I tried to reproduce it with a simple example model and that was successful.

The example model can be found in the attachment. This model also contains a mini local Git repository, containing all the steps I did. In this way it's easy to follow what I did.

Logging is also attached. The time stamps of the logging can be matched with the local Git repository of the example model.