The semantic constraint checkConcernUsageFramedConcernSpecialization in the SysML v2 Specification only requires that framed concerns (i.e., concern usages owned by a requirement definition or usage via a framed concern membership) specialize Requirements::RequirementsCheck::concerns. This PR corrects a bug that previously resulted in all concern usages nested in requirement definitions or usages, not just framed concerns, implicitly specializing Requirements::RequirementsCheck::concerns.
The PR also corrects a bug in TypeAdapter::removeUnnecessaryImplicitGeneralTypes that prevented the removal of some unnecessary implicit specializations.
checkConcernUsageFramedConcernSpecializationin the SysML v2 Specification only requires that framed concerns (i.e., concern usages owned by a requirement definition or usage via a framed concern membership) specializeRequirements::RequirementsCheck::concerns. This PR corrects a bug that previously resulted in all concern usages nested in requirement definitions or usages, not just framed concerns, implicitly specializingRequirements::RequirementsCheck::concerns.TypeAdapter::removeUnnecessaryImplicitGeneralTypesthat prevented the removal of some unnecessary implicit specializations.