fix: validate contract secType on null

[Romazes]

Description

This update introduces a validation step to ensure that contract.SecType is not null before attempting to retrieve the correct SecurityType of the contract. If contract.SecType is null, the update will instead invoke the GetContractDetails() method using the comboLeg.ConId to retrieve the necessary details.

Related Issue

N/a

Motivation and Context

The current implementation assumes that contract.SecType is always populated, which may not be the case in certain scenarios. This can lead to incorrect or failed attempts to retrieve the SecurityType of a contract. By validating that contract.SecType is not null, we ensure that the logic for determining the SecurityType is robust and accurate. If contract.SecType is null, we use the GetContractDetails() method as a fallback mechanism, using comboLeg.ConId to retrieve the required information.

Requires Documentation Change

N/A

How Has This Been Tested?

• run existing tests with ComboOrders

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! 👍