refactor: split subscribe ticker and candle channels

[RafilxTenfen]

Description

• Split subscription of ticker and candle channels for the following providers: Okx, Binance, Huobi, and Kraken
• Add error check for websocket.CloseAbnormalClosure to Kraken when EOF occurs to avoid having the following
  

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added appropriate labels to the PR
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[adamewozniak]

Nice! Just left a few minor suggestions - let's merge this before #611

[alexanderbez]

LGTM. Just one minor nit

[adamewozniak]

LGTM - what do you think about adding SubscribeCurrencyPairs to the interface?

[RafilxTenfen]

LGTM - what do you think about adding SubscribeCurrencyPairs to the interface?

I thought about that, but what about Osmosis? who doesn't have websocket
@adamewozniak

[adamewozniak]

LGTM - what do you think about adding SubscribeCurrencyPairs to the interface?

I thought about that, but what about Osmosis? who doesn't have websocket @adamewozniak

Could put in a no-op, not sure what best practice is to do here. Imo it might be easier for library users (peggo) to assume that the method will be implemented on all providers. Then again, making interfaces as least specific to implementations as possible also makes sense.
cc : @alexanderbez

[alexanderbez]

I imagine we could add SubscribeCurrencyPairs to our interface. In osmosis and others that dont provide websockets, can we have them safely perform a no-op?

[alexanderbez]

Shall we merge this PR or do we want to make further tweaks?

[adamewozniak]

Shall we merge this PR or do we want to make further tweaks?

imo we can merge, I can update the interface in #611 later today
cc : @RafilxTenfen