fix(kuma-cp): using policy name with "." causes hash to be inserted in the wrong place on the zone

[lobkovilya]

Since we allow a dot in the policy name, we can't use functions like CoreNameToK8sName that try to parse the name and make assumptions based on .<namespace> suffix.

Checklist prior to review

• Link to relevant issue as well as docs and UI issues -- Fix Using policy name with "." causes hash to be inserted in the wrong place on the zone #8167
• 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) --

[lahabana]

Ok I'm completely confused with names. Can we have a doc that describes what happens to names between global and zones in all cases (global k8s, global universal, zone k8s, zone universal) ?

[lobkovilya]

Sure, do you think it should be a kuma-website doc or a more developer-oriented doc in this repo?

[lobkovilya]

@lahabana I pushed the doc under the docs/guides for now, please check if it makes sense to you