Clarify behavior of mstro_init arguments vs. environment variable specified values

@sarmany1 reported unexpected behavior as follows:

export MSTRO_COMPONENT_NAME=compName1
mstro_init(workflowName, compName2, 0);

Maestro will understand that the component name is compName1 and will ignore what is passed in the init function.