Seed security prices by default

Expected Behavior

• Add new algorithm setting, enabled by default, for security seed. If enabled after a security is added we should seed an initial historical price to them

Actual Behavior

• Security currently do not have an initial price set

Potential Solution

• After universe selection, for all security additions changes, we can run them through a history request to see their initial price.
  See related GetLastKnownPrices, currently supports a single asset, we want to run history requests in parallel -> universe selection of 500 assets can't seed sequentially

Reproducing the Problem

N/A

System Information

N/A

Checklist

• I have completely filled out this template
• I have confirmed that this issue exists on the current master branch
• I have confirmed that this is not a duplicate issue by searching issues

• I have provided detailed steps to reproduce the issue

Start by reading the existing GetLastKnownPrices implementation and the universe-selection path where security additions are handled. Trace how an initial historical price could be requested for newly added securities, including parallel requests for large selections. Done means a default-enabled setting seeds an initial price for each added security without sequentially processing a 500-asset universe.