Inbound `proxyResourceName` doesn't exactly match with envoy stats

[schogges]

Kuma Version

2.12

Describe the bug

With features-unified-resource-naming enabled on a DP and using the /_layout endpoint to fetch the traffic layout of the DP we receive a list of inbounds and outbounds. The new layout simplifies the mapping of envoy stats with inbounds and outbounds a lot, but there is a tiny detail that we still have to fix in the data-layer of the GUI.
Given an inbound with a proxyResourceName of self_inbound_http and a port of 5050, we have to replace the section name http with 5050 (=> self_inbound_5050) to correctly map the respective envoy stats to the specific inbound. It would be great if we'd just receive the proxyResourceName that exactly matches with the envoy stats.

To Reproduce

kumactl install control-plane --set dataPlane.features.unifiedResourceNaming=true | kubectl apply -f -
kubectl apply -f https://raw.githubusercontent.com/kumahq/kuma-counter-demo/refs/heads/main/k8s/000-with-kuma.yaml

Check the inbound stats of the DPs (demo-app and kv) and search/filter for self_inbound_5050 and self_inbound_http

Expected behavior

No response

Additional context (optional)

No response