Weaving implementation classes that have subtypes broken

[Matthias Schoettle]

Consider the following example based on the Command concern (NetworkCommand in particular).

1. Create a concern with an aspect
2. Import java.lang.Runnable
3. Reuse Command and select NetworkCommand
4. Weave

An exception will occur. The reason seems to be that the weaver does not properly update the superType references.

[Matthias Schoettle]

Resolves #355: Adds updating of superTypes references to the ReferenceUpdater to perform it in a unique place. Therefore, InheritanceWeaver is removed and when shallow copying a class, the superTypes are just copied (since they are updated at the end).

→ <<cset baaa02556607>>

[Matthias Schoettle]

References #355: Adds back weaving of inheritances. This is required for classes that were mapped in order for the super types to be copied over. When updating the references later, we need to ensure that duplicates are removed.

→ <<cset 6999d92412fe>>