fix(kuma-cp): don't configure RBAC rules on Prometheus listener

[lobkovilya]

This issue is currently blocking us from fully switching from TrafficPermission to MeshTrafficPermissions.

After a discussion with @lahabana we want to stop treating Prometheus listeners as an inbound for "fake" service. Instead MeshMetric policy when implemented should contain a configuration of what service is allowed to access the Prometheus listener.

Checklist prior to review

• Link to relevant issue as well as docs and UI issues -- Fix MeshTrafficPermission: prometheus listener doesn't allow traffic with allow-all policy #7412
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Tests (Unit test, E2E tests, manual test on universal and k8s) --
  • Don't forget ci/ labels to run additional/fewer tests
• Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label) --

[slonka]

sounds good, but tests are not passing

[jakubdyszkiewicz]

but this is intentional

https://kuma.io/docs/2.4.x/policies/traffic-metrics/

        tags: # tags that can be referred in Traffic Permission when metrics are secured by mTLS  
          kuma.io/service: dataplane-metrics

edit: read the PR description. This needs docs + UPGRADE.md change if we want to change it