ST6RI-732 Syntax-related resolutions from KerML FTF Ballot #4

This PR implements resolutions of issues from KerML FTF Ballot 4 that called for updates to the KerML abstract syntax.

Resolutions of the following issues are implemented in this PR:

KERML-21 Add property for Annotations owned by an AnnotatingElement
KERML-24 Connector declaration does not allow a feature value
KERML-75 Specify default direction for the ownedParameterMember of a ParameterMembership
KERML-90 The MetadataFeature::metaclass multiplicity is too restrictive
KERML-109 Textual Syntax allows multiple ConjugationParts on a Type
KERML-194 validateRedefinitionDirectionConformance does not account for conjugation
KERML-199 validateMultiplicityRangeBoundResultTypes constraint is too strong
KERML-204 Behavior portions must be classified by the same behavior they are portions of
KERML-232 Additional problems with deriveFeatureType

Resolutions of the following issues are either handled in PR #527 or where otherwise previously implemented:

KERML-7 isDirection, definition, semantics
KERML-61 PrimaryExpressionMember production should generate a ParameterMembership
KERML-154 Directed features inherited from a conjugated type not handled properly
KERML-155 Expression::result has an incorrect subsetting
KERML-248 Error in Expression modelLevelEvaluable operation OCL

Resolutions of the following syntax-related issues did not affect the implementation:

KERML-54 Subsetting::/owningType is mandatory
KERML-138 oclAsType applied to resolveGlobal
KERML-139 OclisKindOf applied to Namespace::resolve()
KERML-167 Typo in Conjugation Description
KERML-169 Feature isDerived metaproperty Typo
KERML-170 checkFeatureSubobjectSpecialization incorrect Font
KERML-173 Classifier Description Typo
KERML-237 Link Participant Plurality Typo in OCL
KERML-242 Typo in checkAssociationBinarySpecialization OCL
KERML-259 Reference to nonexistent class (Superclassification) in OCL rule deriveClassifierOwnedSubclassification

Systems-Modeling / SysML-v2-Pilot-Implementation