feat(xds): introduce deltaXds for configuration exchange

[lukidzi]

Motivation

Envoy supports incremental xDS, which sends only changes rather than the entire state.

Implementation information

Needs fix for warming cluster: kumahq/go-control-plane#15

• Run a Kuma 2-cluster and Kuma- 4 multizone setup with incremental xDS.
• Extracted common logic in each callback to support both communication types.
• Each callback now uses a separate map to store connection information, depending on mode, preventing stream conflicts.
• Added a global and dataplane-only flag to toggle incremental xDS for all DPPs or a single DPP.
• Added config for Ingress and Egress to support deltaXds
• Added a new section Envoy to Dataplane/ZoneIngress/ZoneEgress resource to be able to enable delta for single Sidecar
• Introduced Experimental config that allows enabling deltaXds for all zone

Note

Increased the memory of control-plane since with delta it requires more memory

Supporting documentation

Fix ##13366

[github-actions]

Reviewer Checklist

🔍 Each of these sections need to be checked by the reviewer of the PR 🔍:
If something doesn't apply please check the box and add a justification if the reason is non obvious.

• Is the PR title satisfactory? Is this part of a larger feature and should be grouped using > Changelog?
• PR description is clear and complete. It Links 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 an image registry)
• IPv6 is taken into account (.e.g: no string concatenation of host port)
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • Don't forget ci/ labels to run additional/fewer tests
• Does this contain a change that needs to be notified to users? In this case, UPGRADE.md should be updated.
• 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)

[slonka]

Needs fix for warming cluster: kumahq/go-control-plane#15

are we waiting for this?

[lukidzi]

Needs fix for warming cluster: kumahq/go-control-plane#15

are we waiting for this?

I've just merged it and relased. Ready to review

[slonka]

It's quite big PR, I'll have another round tomorrow

[slonka]

In general I think it's fine. I'm thinking about migration - is per DPP annotation enough? Would we want something per namespace? 🤔