[DEFECT] RFE scoring (avg and std scoring) should be computed for each realization

Thank you for the defect report

[X] I am using the latest version of RAVEN.
[X] I have read the Wiki.
[X] I have created a minimum, reproducible example that demonstrates the defect.

Defect Description

RFE scoring (avg and std scoring) should be computed for each realization. This causes an inconsistency between the RFE-DMDc and the GA-DMDc approach documented in the Feature Selection algorithm presented in the IES report released in July 2023.

Steps to Reproduce

N/A

Expected Behavior

RFE scoring (avg and std scoring) should be computed for each realization.

Screenshots and Input Files

N/A

OS

MacOS

OS Version

No response

Dependency Manager

CONDA

For Change Control Board: Issue Review

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

For Change Control Board: Issue Closure

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

idaholab / raven

[DEFECT] RFE scoring (avg and std scoring) should be computed for each realization #2230