[DEFECT] Fix Numpy Future Warning

[dylanjm]

---

Defect Description

Describe the defect

What did you expect to see happen?

I am seeing this warning when running heron:

/scratch/mcdodyla/TEAL/src/main.py:411: FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this will be interpreted as an array index, `arr[np.array(seq)]`, which will result either in an error or a different result.
  projCf[decomissionMask] += lifeCf[-1] * taxMult * np.power(inflRate, -1*years[decomissionMask])

which appears to be talking about this portion of code:

  if operatingYears[-1] < years[-1]:
    decomissionMask[0] = np.hstack((decomissionMask[0],np.atleast_1d(operatingYears[-1]+1)))
  if not pyomoVar:
    projCf[decomissionMask] += lifeCf[-1] * taxMult * np.power(inflRate, -1*years[decomissionMask])
  else:
    for i in range(len(decomissionMask[0])):
      projCf[decomissionMask[0][i]] += lifeCf[-1] * taxMult * np.power(inflRate, -1*years[decomissionMask[0][I]])

We should fix this before it breaks or gives us wrong answers.

---

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• [x] 1. Is it tagged with a type: defect or task?
• [x] 2. Is it tagged with a priority: critical, normal or minor?
• [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
• [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• [x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

---

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

• [x] 1. If the issue is a defect, is the defect fixed?
• [x] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• [x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• [x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• [x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

[dylanjm]

Approved to close vis #61