fix(meshtrace): add support for real resources

[lukidzi]

Motivation

Issue #12045 showed that we didn't configure real resources

Implementation information

e1d1ed7 extracted test string to golden files
f6ae3d1 added unit test showing an issue
e7d8c6c implementation of real resource and generated file

Added a function that loops over real resources to configure listeners for MeshService and MeshMultiZoneService. Since we don't have a kuma.io/service as a destination, we set the output of DestinationName(port), which is used for clusters.

Supporting documentation

Fix #12045

[lahabana]

Why not MES?

[lukidzi]

Since we don't support policies on Egress, thought maybe no point to add it now

[github-actions]

Reviewer Checklist

🔍 Each of these sections need to be checked by the reviewer of the PR 🔍:
If something doesn't apply please check the box and add a justification if the reason is non obvious.

• Is the PR title satisfactory? Is this part of a larger feature and should be grouped using > Changelog?
• PR description is clear and complete. It [Links to relevant issue][1] as well as docs and UI issues
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as an image registry)
• IPv6 is taken into account (.e.g: no string concatenation of host port)
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • Don't forget ci/ labels to run additional/fewer tests
• Does this contain a change that needs to be notified to users? In this case, UPGRADE.md should be updated.
• 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)
  [1]: https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword