Investigate Kubernetes / KEDA usage in v4 and decide v5 story

`func kubernetes` and `func keda` exist in v4, but we don't yet know how
heavily they're used. Pull telemetry from v4, decide whether v5 ships a
Kubernetes/KEDA workload, and if so, scope the implementation work.

## Definition of Done

- [ ] Telemetry pulled for `func kubernetes` + `func keda` subcommands
(last 6-12 months)
- [ ] Usage analysis written up (volume, top commands, customer
segments)
- [ ] Decision recorded: ship in v5, defer, or drop
- [ ] If shipping: follow-up implementation issues opened (workload,
CI, packaging)
- [ ] If dropping: deprecation plan + comms drafted for v4 users

Start by pulling the last 6–12 months of telemetry for the `func kubernetes` and `func keda` subcommands. Write up volume, top commands, and customer segments, then record whether the v5 story is to ship, defer, or drop. If shipping, open workload, CI, and packaging follow-ups; if dropping, draft the v4 deprecation plan and user communications.

Written by the indexing model from the issue text.