Actual_Connection_Binding not properly instantiated in certain situations

[lwrage]

Summary
If a model contains connection declarations that share the same name, instantiation of the Actual_Connection_Binding property may not be instantiated correctly. I.e., a connection instance may be missing the binding property, or the binding may be applied to the wrong connection instance.
A bidirectional access connection will have the error if the property is associated with the first or last segment in the semantic connection.

Steps To Reproduce

1. Instantiate S.i in the model below.
2. Open the instance model.
3. There are two connection instances, but only one of them has the Actual_Connection_Binding property set.

package Issue2913
public
	
	system S
	end S;
	
	system implementation S.i
		subcomponents
			d: data D;
			p: process P.i;
			b: bus;
		connections
			c2: data access p.da <-> d;
		properties
			Actual_Connection_Binding => (reference(b)) applies to c2;
	end S.i;
	
	data D
	end D;
	
	process P
		features
			da: requires data access D;
	end P;
	
	process implementation P.i
		subcomponents
			t: thread T;
		connections
			c1: data access t.da <-> da;
	end P.i;
	
	thread T
		features
			da: requires data access D;
	end T;
	
end Issue2913;

Desktop (please complete the following information):

• OSATE Version: 2.14
• Operating System: macos