Virtual processor without properties is not included in flow latency report

[joeseibel]

If a component is bound to a virtual processor (aka partition) the partition becomes a latency contributor. However, if the partition does not have any property indicate its rate of execution it is not included in the report. It should be included with an indication that its contribution is zero due to missing property values.
Note: in other cases we do include the partition even though the contribution is zero, e.g., when the component bound to it is the first element of a flow.

package partition11
public
	system s1
	end s1;
	
	system implementation s1.i1
		subcomponents
			sub1: system s2;
			sub3: virtual processor {Period => 1 ms;};
			sub18: abstract a1;
			sub19: virtual processor;
		connections
			conn11: feature sub1.f1 -> sub18.f2;
		flows
			etef11: end to end flow sub1.fsource1 -> conn11 -> sub18.fsink1 {Latency => 5 ms .. 6 ms;};
		properties
			Actual_Processor_Binding => (reference (sub3)) applies to sub1;
			Actual_Processor_Binding => (reference (sub19)) applies to sub18;
	end s1.i1;
	
	system s2
		features
			f1: feature;
		flows
			fsource1: flow source f1 {Latency => 1 ms .. 2 ms;};
		properties
			Period => 1 ms;
	end s2;
	
	abstract a1
		features
			f2: feature;
		flows
			fsink1: flow sink f2 {Latency => 3 ms .. 4 ms;};
	end a1;
end partition11;