performance tuning

[DaveSkender]

General performance tuning and test data updates. Highlights:

• add extreme size test data + add more scenarios to bad data
• opportunistically and carefully replace decimal with double for non-monetary calculations to improve performance - see Precisions v. Performance of `decimal` vs `double` #649
• there may be opportunities to do more conversions to double, later

Breaking changes

Many indicators have had either input parameters or output results class properties changed from decimal to double, too many to enumerate here. See documentation for current types. Summary of changes: mods.xlsx

Checklist

• My code follows the existing style, code structure, and naming taxonomy
• I have commented my code, particularly in hard-to-understand areas
• I have performed a self-review of my own code and included any verifying manual calculations
• I have added or updated unit tests that prove my fix is effective or that my feature works, and achieves sufficient code coverage. New and existing unit tests pass locally and in the build (below) with my changes
• My changes generate no new warnings and running code analysis does not produce any issues
• I have added or run the performance tests that depict optimal execution times
• I have made corresponding changes to the documentation

[github-actions]

This Pull Request has been automatically locked since there has not been any recent activity after it was closed. Please open a new Issue for related bugs.