Extract automated lineage from some IFPC Command Tasks (unused, chmod, cp, mv, rm)

This is a follow up to https://ideas.ibm.com/ideas/DATALIN-I-60 that asks for automated extraction of all Command Tasks invoked by informatica power center. Since IFPC developers can invoke any executable in the command task, it is technically difficult to solve. However, there are a sufficiently large number of simple command tasks that could be resolved by Manta automatically. In addition there are also a sufficient number of Command tasks that are not involved in lineage and should be ignored by Manta without generating any warnings.

In our analysis of over 52900 Command Tasks used at our organization, we found that 75.19% do not mention any command at all. Manta should ignore these and not generate any warnings. For example:

<TASK DESCRIPTION ="" NAME ="presession_variable_assignment" REUSABLE ="NO" TYPE ="Command" VERSIONNUMBER ="2">                     <ATTRIBUTE NAME ="Fail task if any command fails" VALUE ="NO"/>                     <ATTRIBUTE NAME ="Recovery Strategy" VALUE ="Fail task and continue workflow"/>                 </TASK>

In addition, we found over 2000 use simple commands like so:

1. chmod -f 777 $PMSourceFileDir/021/* - these can be ignored sinvce they have no lineage impact
2. cp /fin_sys/fast/tgt/FAST_LS_TXNS_STAT.txt /fin_sys/efi/src/FAST_LS_TXNS_STAT.txt - this has a lineage impact and can be modelled
3. mv $InputFileName_PREV $OutputFileName_CURR - this has a lineage impact and can be modelled
4. rm -f $PMCacheDir/$ParamLKPCACHEFLNM*.* - this has a lineage impact and can be modelled