Feature: Deployment descriptor and README for weather agent and weather tool

[esnible]

Summary

This PR follows the approach of #186 by introducing Kubernetes deployment descriptors.

I use these to quickly spin up a working weather agent for testing. The examples are also documented, which should help humans and LLMs understand how Kagenti deployments should look.

(Optional) Testing Instructions

• kubectl apply -f mcp/weather_tool/deployment/k8s.yaml
• kubectl apply -f a2a/weather_service/deployment/k8s.yaml
• Reload the Kagenti Agent page. The weather service should be present, start chatting with it.

[cwiklik]

Well-structured PR adding production-ready Kubernetes deployment examples for the weather service (A2A) and weather tool (MCP). Security best practices are consistently applied: non-root containers, dropped capabilities, seccomp profiles, dedicated ServiceAccounts, resource limits. The READMEs provide clear deployment instructions with multiple paths (local dev, UI, kubectl).

Areas reviewed: YAML/K8s, Docs, Security, .dockerignore
Commits: 4 commits, all signed-off ✓
CI status: All passing ✓

Suggestions (non-blocking):

• Consider adding a readiness probe to the weather tool manifest (acknowledged in comment already) — since these examples get copied, showing the full pattern helps.
• imagePullPolicy: Always makes sense for alpha tags; a brief comment noting IfNotPresent for stable releases could help users adapting the example.

Good fix in currency_converter aligning the commented Secret example to LLM_API_KEY. Excellent security context pattern throughout — great reference material.