[TASK] "Recurring" Capex

Issue Description

Is your feature request related to a problem? Please describe.

Currently there is no way to discount a Recurring expenditure. The capabilities are all the ones in the Capex cash flow model ( we would need a sort of a recurring "Capex" expenditure). For example, in the lifetime of the project there might be expenditure that might be "recurrent" (e.g. every month I buy gasoline for my car), that have the possibility to be discounted.

Describe the solution you'd like The possibility to have "recurrent" Capex expenditure or recurring with discounting strategy.

Describe alternatives you've considered Use the <Repetitions>xxx</Repetitions> and create a new component to "mimic" the recurrent expenditure

For Change Control Board: Issue Review

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

[ ] 1. Is it tagged with a type: defect or task?
[ ] 2. Is it tagged with a priority: critical, normal or minor?
[ ] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[ ] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] 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.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
[ ] 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)?
[ ] 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)?
[ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

idaholab / TEAL