Fix tests and small refactoring to avoid duplicate code

[arodus]

Description

Not all tests were running properly, this PR fixes the issue and refactors the tests so less duplicated code is being used.
The classes could be renamed as the different brokerages are not existing anymore but they're still testing the different categories and I didn't have a better idea for a name.

Related Issue

Part of QuantConnect/Lean#5898

Motivation and Context

Failing tests

Requires Documentation Change

How Has This Been Tested?

Running the tests

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]

Nice, ty! Leaving a few minor comments

[Martin-Molinero]

Thank you! 🎸