PM-667 enabled transfers for DAX jobs, since the dax jobs are now
launched in the scratch directory on the local site.
PM-667 removed commented out code.
PM-667 We need to track the conf file option in the PlannerOptions.
This enables us to detect whether a user has specified a properties
file as a conf option in the DAX job in the DAX. If that is the case,
then the dax is setup to run with that properties file and not the one
inherited from outer workflow.
PM-667 added a dynamic hierarchial workflow example that highlight how
to have a dax generation job in the workflow.
PM-667 added a test case for it.
Merge branch 'PM-667' Added example, test case and completed changes
to code.