feature: map exchange string to primary exchange on level one ticks

[Romazes]

Description

Adds saleCondition and exchange parameters to LevelOneMarketData.UpdateQuote and normalizes the exchange string through GetPrimaryExchange on both UpdateQuote and UpdateLastTrade. Resulting ticks now carry the canonical primary exchange name (e.g. "T" → "NASDAQ", "Z" → "BATS") instead of the raw broker-provided code.

Related Issue

N/A

Motivation and Context

Brokerage providers send exchange identifiers as short codes (T, Z, N, P, ...). Without normalization, downstream consumers see the raw code and have to map it themselves. Centralizing the mapping at tick-construction time gives a consistent Tick.Exchange value across the engine and matches the behavior already used by UpdateLastTrade's sibling code paths.

Requires Documentation Change

No.

How Has This Been Tested?

Added a combined NUnit test in Tests/Brokerages/LevelOneOrderBook/LevelOneMarketDataTests.cs:

• LevelOneMarketDataShouldMapExchangeStringOnPublishedTicks subscribes to BaseDataReceived and asserts the resulting Tick.Exchange for both the quote tick (UpdateQuote) and the trade tick (UpdateLastTrade).
• Covered cases: "T" → "NASDAQ", "Z" → "BATS", "N" → "NYSE", "P" → "ARCA", "" → "", null → "".

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!