fix(kuma-cp): use GetConsistent store when validating default mesh resources

[lukidzi]

Checklist prior to review

When validating the default resources for the mesh when using an eventually consistent store there might be an issue that resources won't be available on the read replica at the time of validation. This ensures that resources are checked from a write replica.

• Link to relevant issue as well as docs and UI issues -- fix: Error during creation of new mesh when using ReadOnly replica #7911
• 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) --
• 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) --
• Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?