Fix crypto future margin model to reflect margin used

[jhonabreul]

Description

Fix crypto future margin model to reflect margin used following BInance and Bybit patterns.

These exchanges have two different concepts:

1. Margin used: the same as the initial margin requirement which is deducted from the available margin after opening a position.
2. Maintenance margin: the minimum margin required to keep positions open.
   • This has nothing to do with margin used and is not used for it's calculations, like Lean does.

Margin calls will be now more inaccurate for as a workaround, users can set a custom margin call model with an adjusted buffer (Portfolio.MarginCallModel = new DefaultMarginCallModel(Portfolio, DefaultOrderProperties, customBuffer);) or even disabling margin calls by using the null margin call model (MarginCallModel.Null)

Related Issue

Closes #7604
Closes #7816

Motivation and Context

Requires Documentation Change

How Has This Been Tested?

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>