Added stronghold auto-discovery from kube API

[trublast]

If the user has not specified Stronghold access parameters via environment variables or command-line arguments, an attempt will be made to retrieve parameters from the Kubernetes cluster using the current kubconfig context.

[Copilot]

Pull request overview

Adds an auto-discovery mechanism for Stronghold connection parameters by querying the current Kubernetes cluster context when the user hasn’t provided configuration explicitly, and wires this discovery into the stronghold command execution path.

Changes:

• Added Kubernetes-based discovery logic to derive Stronghold address, token, and CA cert bytes and apply them via environment variables.
• Added unit tests for helper functions and the “skip when already configured” path.
• Updated stronghold command routing so all Stronghold command entrypoints run the discovery step before delegating to the Stronghold/Vault CLI.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
internal/stronghold/discovery.go	Implements kube API discovery and applies discovered Stronghold env vars before running CLI.
internal/stronghold/discovery_test.go	Adds unit tests for discovery helpers and configured-skip behavior.
cmd/commands/stronghold.go	Wraps Stronghold command execution to run discovery before vaultcommand.Run.
cmd/commands/stronghold_commands.go	Routes generated subcommands through the new Stronghold runner (with discovery).

---

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