feat(kuma-cp): inbound name should be taken from pod instead of service

[Automaat]

Motivation

At this moment we are taking inbound name from service port name. In order to get rid of kuma.io/service we need to take name from pod port name. Since we are not using name at the moment, it is safe to switch this.

[Automaat]

this extracts naming part from: #12760 as I am still looking into failing tests, and this should work 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 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)

[lobkovilya]

btw it's used here, but I guess it won't be affected by the change?

[lobkovilya]

LGTM, please open an issue to document this behaviour, it looks like today we don't explain in the docs where ports on DPP are coming from