feature: expand e2e coverage across CLI surface

[atkrad]

e2e covers cluster up / status / down and one deploy/delete per scenario. plan, logs, resolve, list, status, and cluster kubeconfig can still regress against a live cluster.

Add cases on the shared Kind cluster, not a second create/destroy cycle:

• cluster kubeconfig (path and --raw)
• plan (offline and live)
• list / status after deploy
• logs for the smoke workload
• resolve against the fixture

Workload-shaped cases stay auto-discovered from internal/e2e/testdata/. Offline golden tests stay in integration.

Grow incrementally. Do not hit every flag in one giant test.

[atkrad]

Note: parent #37 now uses testify/suite (E2ESuite). Expanding CLI coverage means adding methods to that suite (or a sibling suite in the same package). No new cluster create/destroy per command -- they all share SetupSuite's cluster and s.kcPath.