fix(kds): set error when KDS clients fails in goroutine

[lukidzi]

Checklist prior to review

We are using bi-directional GRPC for the communication between zone and global. KDS might fail when trying to connect with the global and because of this, the zone might not be in sync with Global resources. Because of that, we are using a resilient component which is responsible for starting the code again in case of errors. It works well when an error is returned. But the zone code wasn't returning an error and that caused the component to not start again.

I am not sure how to exactly test it yet.

• Link to relevant issue as well as docs and UI issues -- fix: [KDS] When clients try to reconnect and there is error connection is broken #7723
• 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?

[github-actions]

backporting to release-2.0 with action

backporting to release-2.2 with action
backporting to release-2.3 with action
backporting to release-2.4 with action

[github-actions]

backporting to release-2.1 with action