SYSML2_ — Each FlowConnectionUsage owned by PartUsage subsets 3 features

In current implementation each FlowConnectionUsage owned by PartUsage subsets (automatically) 3 features:
FlowConnectionUsage::flowConnections
PartUsage::subparts
ActionUsage::ownedActions

This could be optimized for the sake of model size.
Maybe it would be better idea to introduce
Part::Part::ownedFlows :> ownedActions, subparts, flowConections
and define something like CheckFlowConnectionSubFlowSpecialization constraint?

Pass-through note to Ed: This is one of the issues from the compiled list that we talked about - issue # SYSML2-1758 on DS side