Make sure component execution result can be communicated to the container

This is related to the RETURNs special property type.

From HongChungYi:

[3/10/16, 22:55:02] hongchun.yi: @ Francis
[3/10/16, 22:55:05] hongchun.yi: On 3/7/16, at 22:36, Zhao Jin(赵进)-Component Team wrote:
> Hi Francis,
I have some questions about the RETURN value of components:
In the old components XML:
<RETURNS>
<RETURN NAME="NB_LINE" TYPE="id_Integer" AVAILABILITY="AFTER" />
<RETURN NAME="FILE_NAME" TYPE="id_String" AVAILABILITY="FLOW" />
</RETURNS>

In the new Framework:

returns = ComponentPropertyFactory.newReturnsProperty();
ComponentPropertyFactory.newReturnProperty(returns, SchemaElement.Type.INT, "NB_LINE");

How can we set "AVAILABILITY" ? (it is useless for component side. it was used by studio side).
"AFTER" means we set the globalMap key-value in the end part of component.
"FLOW" means we set the globalMap key-value in the main part of component.

After dropping globalMap in the new framework.
How can we shared the return value with other component during the runtime?

globalMap.get("tSalesforceInput_1_NB_LINE")
This is the way we get the return value in the old framework.
I think it also should be work after new framework. Because we need migrate the old job.
And this is the same problem with shared connection instance( https://jira.talendforge.org/browse/TCOMP-110 )
Those should be considered together.