feat: price-feeder: telemetry additions

[adamewozniak]

Description

Adds some measurements for Websocket reconnection attempts & candle / ticker messages being received

closes: #637

---

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]

Just using the only constants that carry the names of the providers here - maybe we should have an additional set of constants in the providers package, but that seems a bit overkill for this

[adamewozniak]

Would also like @RafilxTenfen 's input on any other metrics that might be useful

[RafilxTenfen]

@adamewozniak

The telemetry is going to increase the count when peggo uses the price-feeder?
If so, do you think we should differentiate the usage with an key?

[RafilxTenfen]

What do you think about adding telemetry to subscribedPairs? like:

       ....
       	p.setSubscribedPairs(cps...)
	telemetry.IncrCounter(
		float32(len(cps)),
		"websocket",
		"subscribe",
		"currency_pairs",
		"provider",
		config.ProviderBinance,
	)

[adamewozniak]

@adamewozniak

The telemetry is going to increase the count when peggo uses the price-feeder? If so, do you think we should differentiate the usage with an key?

iirc it would only count if telemetry were enabled (e.g. if you called telemetry.New), so I don't really think we need a price.feeder key to differentiate, I don't think peggo has its own telemetry

[toteki]

Looks good (but give it a final check before merging)