bybit: add trade spot and trade option websocket msgspec schemas

[davidsblom]

Pull Request

Add msgspec schema's for trade messages for spot and option instruments, due to the L field being unique to futures and id being unique to options.

Type of change

Delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How has this change been tested?

Locally listening to trade and quote ticks for the Bybit exchange.

[cjdsellers]

Thanks for the help @davidsblom!

I think even more efficient if we just define some optional fields for the trade message, rather than the entirely separate messages per instrument. I'll merge as is though if this was working for you, and we can always refactor.

[davidsblom]

Great! Optional fields are needed much cleaner.

The important fix is the use of the partial instead of a lambda. The lambda functions were being overwritten somehow when using multiple product types. Any idea how that is even possible?

[davidsblom]

Found the answer here: https://stackoverflow.com/questions/50298582/why-does-python-asyncio-loop-call-soon-overwrite-data

When the lambda function is called, it will use the values bound by those names in the outer scope at that time of the call, not the values they had when the lambda was defined.