feat(internal_metrics source): Instrument few more components with metrics

[Alexx-G]

This PR instruments few components with metrics following checklist from #2007
I've followed initial implementation from #1953

I have few open questions though:

• Is there a convention for internal events naming? I've got a bit confused. E.g. ElasticSearchEventReceived defined for sink component, however most internal events define *Sent events for sinks and *Received events for sources. And since corresponding metric name in most places is events|bytes_processed, it's a bit confusing adding metrics for the first time.
• Would it be possible to include component name as metric tag? Since same component type can be used multiple times in the config, it's super useful to be able to distinguish them.

[lukesteensen]

These look great, thanks so much @Alexx-G!

[binarylogic]

Thanks @Alexx-G!

[Alexx-G]

Thanks for reviewing it @lukesteensen !
@binarylogic @lukesteensen Would it be possible to include component name as metric tag? It would slightly increase metrics volume, on the other hand it would allow distinguishing metrics for same component used multiple times (e.g. it's possible to flush data to 3 different Kafka sinks with different SLA - e.g. self provisioned kafka vs MSK, thus aggregated view doesn't tell which one fails more often).

[binarylogic]

@Alexx-G I've opened #2660 for that. It's a caveat we noted during the initial implementation and hope to solve in the future. Until then, we can attempt to manually pass this data to the event. I'm not sure if that's possible. Ideally, we'd carry over the tracing context as noted in that issue.