This PR corrects several bugs in the implementation of transformation code satisfying semantic constraints from the KerML and SysML specifications

ST6RI-857 Cross feature implicit subsetting is incorrect

This bug resulted in owned cross features subsetting Base::things when the implied typing by their owning end feature's type meant they should subset Base::dataValues, Occurrence::occurrences or Object::objects. It was fixed by moving the call to addOwnedCrossFeatureSpecialization in FeatureAdapter.addDefaultGeneralType to before the call super.addDefaultGeneralType. In this way, the implied owned typing for a cross feature is now added before the determination of the default subsetting, which is based on owned typing.

ST6RI-858 Incorrect implicit specialization of feature chain invocation result

This bug resulted in the result parameter of an invocation expression not properly redefining the result parameter of its instantiatedType if that type was a feature chain and the feature target of the chain did not have an owned result parameter. It was fixed by replacing the call to getSupertypesOf with getGeneralTypesOf in FeatureUtil.getResultParameterOf.

ST6RI-860 ConnectionUsages, ViewUsages and RenderingUsages should subset subparts

This bug was that composite ConnectionUsages, ViewUsages and RenderingUsages that were features of ItemDefinitions or ItemUsages were not implicitly subsetting Item::subparts. It was fixed by updating the relevant adapter classes to override addDefaultGeneralTypes to handle being a subpart.

ST6RI-861 TransitionUsage payload parameter subsetting is incorrect

This bug was that the payload parameter of a TransitionUsage was implicitly subsetting directly the payload parameter of the triggerAction of the TransitionUsage, rather than subsetting a feature chain of the triggerAction and its payload parameter. This was corrected in the ReferenceUsageAdapter.addDefaultGeneralType method.