feat(kuma-cp): require kuma.io/origin: zone label when creating zone-origination policies

[lobkovilya]

Checklist prior to review

• Link to relevant issue as well as docs and UI issues -- fix It's possible to remove global-originated policy on zone #8934
• 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) --

[jakubdyszkiewicz]

This is optional UX feature. I remember we talked about disabling it via env var if someone don't want to have this validation. Should we introduce such env var?