Run each measure step of workflow in clean ruby environment to avoid cross measure interactions

[DavidGoldwasser]

We can update our measure writing guide and internal practices to minimize interaction, but it can be hard to completely get rid of it, in particular when using workflow with measures developed by different organizations or older and newer measures from the same organization that may be out of sync with each other.

If there is a performance hit for this, then it could be an option that is passed in that defaults to false.

[shorowit]

@DavidGoldwasser Can you give examples of the kinds of interactions that could cause problems?

[DavidGoldwasser]

1. Multiple measures have the same named resource file loaded but the content of the resources files between the measures are not the same.
2. Even making the file names unique does not always protect against. The module names being the same even on files of different names still creates issues.
3. In some cases even the module names are unique but the model is loaded into the model and then called with a non-explicit name (just the method name. vs. including the module name). In this case the earlier loaded method by that name is called instead of the method from the module loaded by this measure.

The most common time this is found is where a custom version of a measure was altered but maintains modified or outdated resources that interacts with other measures in the workflow. This can be minimized with good coding practices but not fully eliminated. I've hit this a number of times where I've had to try and modify unfamiliar measures and resource files to get analysis to run. I only notice it when I get measure errors, but it is possible this is hit at times producing simulations that run but with un-expected results.