Clone configuration on re-subscription

[jhonabreul]

Description

Clone configuration on re-subscription. When re-subscribing a request after a fill forward resolution change, clone SubscriptionDataConfig to avoid memory access race conditions, like setting the MappedSymbol when emitting new tradable date events.

This can happen because when removing the existing subscription, the produce enumerators are not stopped instantly since they run on separate threads, so for a little while we might have 2 SubscriptionDataReaders for the same configuration.

Related Issue

Closes #7818

Motivation and Context

Requires Documentation Change

How Has This Been Tested?

Backtesting and existing 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>

[Martin-Molinero]

Thank you 👍