feat(k8s): do not set mesh owner reference on synced resources

[jakubdyszkiewicz]

Checklist prior to review

I investigated KDS NACKs in E2E tests and all of them are caused by mesh owner reference.
What is interesting is that we don't set Mesh owner reference on Universal (because we go directly thorough store, not resource manager), that's why the only NACKs we saw were from Kube zones.

Setting mesh owner reference caused the following problems:

• Policy is synced before mesh - fails because mesh is not present so we cannot set an owner
• Resource not found on delete - fails because resource was first deleted by owner mechanism

Additionally, I disabled secret delete validation on synced resources. This also caused a race when you delete Secret before Mesh. It was also only applied on Kube because of same reasons (store vs manager).

After this change, I see 0 NACKs on KDS in the multizone suite.

Also, first I tried ordering resources over KDS, but not waiting for ACK resulted races as well. I think it's just more correct to trust the source of truth (other CP that manages resource).

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

[lobkovilya]

Nice! I like the idea 👍