Use independent pods / deployments for each container service

[jrbe228]

Currently the runtime deploys as 3 containers within 1 pod -

Eventually we would want 1 container per pod (plus any helpful sidecars) for independent scaling and resilience. Then pod-to-pod communication happens via ClusterIP services. I started a PR for that purpose.

This topic may be a longer-term goal, per the reasons explained here.

[EItanya]

As we think about transitioning kagent into a product which can be run in production this will become more important. As I've mentioned before the pre-cursors should be:

1. Regression testing which ensures this change does not break existing functionality.
2. The continued ability to run as 1 pod for demo purposes