Smoke test important DevSpace profiles

[michaelw]

Summary

Extend smoke coverage so the expensive e2e path exercises the important DevSpace profile combinations, not only the default deployment.

Context

PR #7 adds make smoke and a provider-backed e2e driver that validates the default advertised deploy path against an ephemeral cluster. Several repo profiles enable meaningful variants that should also be validated periodically, especially profiles that change installed components or user-facing diagnostics.

Initial profile targets

• local-test
• with-o11y
• o11y-grafana
• o11y-addons
• data-service profiles such as local-psql, local-redis, and local-es
• host integration hooks where practical, without requiring unsafe default host mutation in CI

Acceptance criteria

• Smoke e2e can run a configurable profile matrix against an ephemeral cluster.
• Each matrix entry forces commands through the temporary smoke kubeconfig and never uses the user's default kubeconfig.
• The matrix includes at least local-test and o11y-grafana, plus any other profiles required to cover observability and optional install diagnostics.
• CI runs the profile smoke matrix nightly or manually, without putting the full matrix in the default PR hot path.
• PRs labeled smoke run the profile coverage, or clearly document any split between default smoke and profile smoke.
• Failures report which profile combination failed and include the same useful Kubernetes diagnostics as the default smoke path.
• Documentation explains how to run one profile combination locally and how to run the full profile matrix.

Notes

• Keep nontrivial orchestration in Go rather than long shell loops.
• Avoid destructive or host-mutating hooks by default in CI unless the test explicitly opts into them and cleans up after itself.
• Consider whether profile combinations should be additive DevSpace args, separate smoke scenarios, or a small table-driven scenario model in the e2e driver.