feat: pinnable context names per profile

[juliamertz]

to prevent deploying to the wrong cluster you can now enforce a specific context name per profile with something like

contextMappings:
    local: k3d-brainpod-local
    test: brainpod-test
    ...

[Copilot]

Pull request overview

Adds an optional safety check to prevent deploying with the “wrong” active Kubernetes context by allowing profiles to pin an expected current-context name via contextMappings.

Changes:

• Introduces contextMappings in configuration to map profile names to expected kubeconfig context names.
• Passes the selected profile into the deploy command so it can enforce the expected context.
• Adds deploy-time validation that compares the active kubeconfig context to the configured expected value and errors on mismatch.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/main.rs	Threads profile through to cmd::deploy::run(...) so deploy can apply profile-specific checks.
src/config.rs	Adds context_mappings (contextMappings in YAML) to the config model with a default empty map.
src/cmd/deploy.rs	Implements context enforcement and introduces contextual error types for mismatch/missing kube context.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dmeijboom]

LGTM (one comment)