fix(kuma-cp): properly match policies to gateway when calling _rules endpoint

[Automaat]

When we call inspect API _rules endpoint for MeshGateway resource, we create fake dpp without meta that is only used to pick proper gateway for matching. With this change, we are adding gateway meta to it, and we are filtering gateways by zone to pick only gateways from the same zone. Moreover, we are now matching policies by zone not only for dpp but also for MeshGateway

Fixes: #11455

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) --
  • 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) --

[Automaat]

I think there might be a bigger issue here. When we are selecting gateway we are looking only at selector, and when we run this on global we ignore the fact that we could have synced gateways from different zones with the same selector. I think that this only affects inspect api on global, but I am not sure

Edit: I've fixed this by adding gateway meta to fake dpp that we create and filtering gateways by this dpp zone