fix(kuma-cp): filter out old dangling zone resources in global

[michaelbeaumont]

Now if there are <zone-name>-prefixes added to hashed versions (which can be reproduced as described below), they are removed initially and later resynced if the zone sends them again.

Checklist prior to review

• Link 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 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) --
  • single zone:
    1. zone CP upgrade 2.6.2
    2. global CP upgrade 2.6.2
    3. see dangling resources
    4. dangling resources still there
    5. global CP upgrade this fix
    6. resources gone
  • multizone:
    1. west CP upgrade 2.6.2
    2. global CP upgrade 2.6.2
    3. dangling resources from west in global and east
    4. east CP upgrade 2.6.2
    5. global CP upgrade this fix
    6. resources gone from global and zones
  • multizone:
    1. west CP upgrade 2.6.2
    2. east CP upgrade 2.6.2
    3. global CP upgrade 2.6.2
    4. dangling resources from both west and east in global and east/west
    5. global CP upgrade this fix
    6. resources gone from global and zones
  • new ZoneIngresses come up fine after this change
• 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) --