fix(kuma-cp) handle missing connection info

[jakubdyszkiewicz]

Summary

https://github.com/kumahq/kuma/pull/2342/files#diff-4e677d8a7546b3383197877f4c14437d4b356b1ef10a13d7c81fdc8e05b45632R65 was merged without resolving the todo.

In a case when we spin down data plane proxy, technically we can remove connection info from the map and still have one more Sync in DP watchdog. When this happens, CP fails.

Documentation

• No docs

Testing

• Unit tests
• E2E tests
• Manual testing on Universal
• Manual testing on Kubernetes

Backwards compatibility

• Add backport-to-stable label if the code is backwards compatible. Otherwise, list breaking changes.

[bartsmykla]

lgtm

[codecov-commenter]

Codecov Report

Merging #2439 (0e84bb3) into master (09fc104) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #2439   +/-   ##
=======================================
  Coverage   52.58%   52.58%           
=======================================
  Files         878      878           
  Lines       47896    47904    +8     
=======================================
+ Hits        25185    25192    +7     
+ Misses      20667    20663    -4     
- Partials     2044     2049    +5     

Impacted Files	Coverage Δ
pkg/xds/sync/dataplane_watchdog.go	0.00% <0.00%> (ø)
pkg/xds/sync/xds_context_builder.go	21.21% <0.00%> (-4.72%)	⬇️
pkg/kds/client/sink.go	47.72% <0.00%> (-4.55%)	⬇️
pkg/mads/v1/client/client.go	41.25% <0.00%> (-2.50%)	⬇️
api/observability/v1/mads.pb.go	34.53% <0.00%> (-1.04%)	⬇️
pkg/core/resources/manager/cache.go	84.41% <0.00%> (+5.19%)	⬆️
pkg/core/bootstrap/autoconfig.go	54.46% <0.00%> (+8.03%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 09fc104...0e84bb3. Read the comment docs.