Add standard metrics to instrument network connections and payload for all receivers

[anubhav21sharma]

Component(s)

receiver/receiverhelper

Is your feature request related to a problem? Please describe.

The current set of standard metrics exposed by all receivers include the number of metrics/logs/traces accepted/refused/failed. This issue is to propose new set of standard metrics that provide a consistent way to instrument the amount of network IO being done by the receivers - including but not limited to number of connections created, number of connections closed, and the size distribution of the payload received.

Describe the solution you'd like

There are some suggestions regarding the potential naming convention for such metrics (thanks to @thompson-tomo) in this PR - 45204.

Why? - I think such metrics provide essential insights into the behavior of any receiver. Establishing a standard way to define them enables developers to adhere to consistent semantics, and decluttering the otel collector's internal telemetry namespace.

Describe alternatives you've considered

No response

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[thompson-tomo]

Note the internal telemetry already has a metric for reciever produced data and what is missing is the consumed data. This might be addressed by #14350

What is interesting is exploring the connection status metrics.