Update Binance currency pairs

[starteleport]

Description

This adds missing Binance symbols to the symbol database.

Related Issue

Closes #7692

Motivation and Context

Some existing Binance trading pairs were absent in the symbol database.

Requires Documentation Change

No

How Has This Been Tested?

This is the metadata change only, so I suppose there is no need to run 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.
• Added tests for new stablecoin, fixed existing.
• All existing tests are passing.
• My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

[AlexCatarino]

We also have a request for GBP-quoted crypto pairs. It's out of the scope of the issue that led to this pull request, but we could add a commit to address it too.

[starteleport]

Actually yes, it's not a complete list of the pairs that are absent. If it's okay to go out of scope here, I could add a broader range of crypto pairs (i.e. all that are absent at the moment)

[Martin-Molinero]

Hey @starteleport ! Thank you for the contribution,
Running the binance toolbox updater will generate the new complete SPDB automatically based on their api see https://github.com/QuantConnect/Lean.Brokerages.Binance/blob/master/QuantConnect.BinanceBrokerage.ToolBox/Program.cs#L70. Could you give it a run?

[starteleport]

@Martin-Molinero done!

[jhonabreul]

Thank you for your contribution! Looks good. Just one comment: why the changes in the Kraken symbols?

[Martin-Molinero]

Thank you @starteleport! Almost there, please revert the kraken SPDB changes like JA noted 👍. There seems to be a few unit tests failing in the PR, possibly related to that change

[starteleport]

Ah, sorry for Kraken bits, they were supposed to be rolled back.

[starteleport]

Also, I'm looking into the failing tests now

[Martin-Molinero]

Nice work! 🚀

[jhonabreul]

Thank you!

[starteleport]

@Martin-Molinero, could you review again, please? I've fixed a typo in a symbol name.

[starteleport]

That's kind of strange. I have OptionChainProviderTests.LiveOptionChainProviderReturnsFutureOptionData failing locally and in my GH fork.

I'm not sure about the reasons, because this seems unrelated. Any ideas? If not, I'll look into that a bit later.

[starteleport]

It looks like the API used during the test is failing:

20240123 20:28:02.303 ERROR:: <GetFutureOptionContractList>d__15.MoveNext(): Failed to retrieve futures options chain from CME, returning empty result (5 / 5) System.Net.Http.HttpRequestException: Response status code does not indicate success: 403 (Forbidden).

Given that there had been quite a few test runs of this test recently, and the throttling inside GetFutureOptionContractList, I suspect that we have hit some rate limiting of the called API.

[Martin-Molinero]

It looks like the API used during the test is failing:

20240123 20:28:02.303 ERROR:: <GetFutureOptionContractList>d__15.MoveNext(): Failed to retrieve futures options chain from CME, returning empty result (5 / 5) System.Net.Http.HttpRequestException: Response status code does not indicate success: 403 (Forbidden).

Given that there had been quite a few test runs of this test recently, and the throttling inside GetFutureOptionContractList, I suspect that we have hit some rate limiting of the called API.

Hey @starteleport! Thank you 🚢
Yes, that unit test has started failing on and off for github CI, unrelated 👍