Feature/49 named fault participation

[chrisbc]

NB rebase this once #66 is merged DONE

• closes Feature: named_fault_participation_rate #49
• amd it closes Epic Feature: enhanced participation rate options #42
• convert CFM named faults to a suitable dataframe
• add named_faults support to FilterParentFaultIds class
• add named _fault support to SolutionParticipation class

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.31%. Comparing base (f635311) to head (8ed3f22).
Report is 2 commits behind head on pre-release.

Additional details and impacted files

@@               Coverage Diff               @@
##           pre-release      #67      +/-   ##
===============================================
+ Coverage        99.29%   99.31%   +0.02%     
===============================================
  Files               23       23              
  Lines             1273     1317      +44     
  Branches            62       68       +6     
===============================================
+ Hits              1264     1308      +44     
  Misses               8        8              
  Partials             1        1              

Flag	Coverage Δ
unittests	99.31% <100.00%> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[chrisdicaprio]

looks good @chrisbc just a comment and a Q (with a scope outside this PR, I think)

[chrisdicaprio]

consider using functools.cache new in py3.9 (which is min python for solvis) https://docs.python.org/3/library/functools.html#functools.cache

[chrisdicaprio]

is there anything that ensures the mapping is only applied to models where it is correct? What happens if a new CFM with new named faults is introduced?