Use same data normalization mode for regular security and benchmark security

[jhonabreul]

Description

If the user adds a given security both as a normal security and as benchmark, use the data normalization mode from the regular security for the benchmark one.

Regression algorithms stats change: those algorithms are adding a security and setting the benchmark to the same one, but the algorithms either set the data normalization mode to Raw explicitly or through adding an option, which adds the underlying with raw data normalization mode. Previous to this change, the benchmark data normalization mode was Adjusted by default.

Related Issue

Closes #7846

Motivation and Context

Requires Documentation Change

How Has This Been Tested?

Regression algorithms

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which improves implementation)
• Performance (non-breaking change which improves performance. Please add associated performance test and results)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Non-functional change (xml comments/documentation/etc)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

[jhonabreul]

Closing since original issue could not be reproduced and we also need the benchmark data to be adjusted so math is not affected by jumps around splits.