MetricsPort: inbound ORPort connections: relays vs. non-relay connections

this got previously submitted on 2022-10-24 #40194 (comment 2849481) but that issue got closed and asked for new specific tickets for each new metric:

From last week's relay meetup we know that tor knows whether an incoming OR connection is from a client or from a relay without looking at the source IP address. https://pad.riseup.net/p/tor-relay-op-meetup-o22-keep From the metrics added in !625 (merged) (merged) we know, that the increased CPU load correlates with an increase in the rate of new inbound OR connections. This rate increases when CPU load increases on exits:

rate(tor_relay_connections{type="OR",state="created",direction="received"}[$__rate_interval])

Could you please add a label for OR connections coming from clients vs. OR connections coming from other relays? This would allow us to confirm that exits get more new inbound connections from clients when CPU load increases.

that new label could be src:

tor_relay_connections_total{type="OR",state="created",direction="received",src="relay"}
tor_relay_connections_total{type="OR",state="created",direction="received",src="non-relay"}
tor_relay_connections{type="OR",state="opened",direction="received",src="relay"}
tor_relay_connections{type="OR",state="opened",direction="received",src="non-relay"}