OMR and Recurring Contract Cost Pages - add duration component for recurring = yes

[jkneifel]

We need to be able to make a recurring cost stop. This is done in energy and water costs and other costs with the unit index because those values can vary by year, but that is not user friendly for a cost that is a binary occurring or not. So we need to include a "duration" of occurrence. So we know if a recurring cost will stop at some point in the future before the end of the study period. Right now we assume that all keep recurring to the end of the study period.

In all cases below, add the duration component to the right of the "occurs every" input and have it display conditional on recurring being yes.

OMR Cost
Recurring Contract Cost

This needs to be passed to the E3 file as the quantity is 1 starting in initial occurrence year and remains 1 through the duration and then becomes zero.

If uploading an existing file, to fill this duration, you use the usage index interval values from the XML. This supersedes issue #173 (which is only focused on annually recurring contract) that is used to bypass this missing value. Once the duration is available for inputting the "interval" in the XML can directly be used to populate the duration. If the interval is blank, then the duration is the remainder of the study period. This can be repeated for all cost subtypes listed above.

[jkneifel]

When upload an existing file, if an annually recurring cost has a non-blank usage index, we need to do the following:
Determine how many years the cost lasts by looking at the duration for which the usage factor = 1.00 (or 100%). In the Federal Financed example, the value is 10 years.
Here is what it looks like in the example:

   <UsageIndex>
      <Intervals>10 years 0 months,Remaining
      </Intervals>
      <Values>1.0,0.0
      </Values>
    </UsageIndex>

Find the interval length in years for which value =1.0 and upload that value to the newly created duration user input.
Note this issue supersedes #173 .

[vsauder-NIST]

Duration should be converted as: first value of > 0.5 until first value after that which is less than 0.5.