feat: add deep-link support for pod exec/terminal via ?view=exec

[justinas-wix]

Summary

Add support for the ?view=exec query parameter on pod detail pages to auto-launch the terminal/exec Activity panel, mirroring the existing ?view=logs deep-link support.

This enables users to share and bookmark direct links to exec into a specific pod:

/c/<cluster>/pods/<namespace>/<pod-name>?view=exec

Motivation

Headlamp already supports ?view=logs for deep-linking to pod logs. This is useful for sharing links from alerting systems, CI/CD pipelines, runbooks, and incident management tools. The same capability for exec/terminal is a natural complement — teams often need to quickly exec into a pod to debug an issue flagged by monitoring.

Changes

frontend/src/components/pod/Details.tsx:

• Added a launchTerminal callback (via useCallback), mirroring the existing launchLogs pattern. It calls Activity.launch() with the Terminal component and dispatches the TERMINAL event with OPENED status.
• Added a useEffect that watches for ?view=exec in the URL query parameters and auto-launches the terminal once the pod data is loaded, using a ref (lastAutoLaunchedPodExec) to prevent duplicate launches — the same pattern used for ?view=logs.
• Refactored the existing inline terminal launch in the POD_TERMINAL header action button to reuse the new launchTerminal callback instead of inlining the Activity.launch() call, keeping the code DRY and consistent with how launchLogs is already used for the logs button.

frontend/src/components/pod/Details.test.tsx (new):

• Added unit tests for both ?view=exec (new) and ?view=logs (existing) auto-launch behavior
• Tests verify Activity.launch is called correctly, not called when param is absent, and not re-triggered on re-renders

Usage

Deep link	Behavior
/c/main/pods/default/my-app?view=logs	Opens log viewer (existing)
/c/main/pods/default/my-app?view=exec	Opens terminal/exec (new)

Test Plan

• Navigate to /c/<cluster>/pods/<namespace>/<pod>?view=exec — terminal Activity panel should auto-open
• Navigate to /c/<cluster>/pods/<namespace>/<pod>?view=logs — log viewer should still auto-open (no regression)
• Navigate to /c/<cluster>/pods/<namespace>/<pod> (no query param) — neither should auto-open
• Click the "Terminal / Exec" header action button on a pod detail page — terminal should open as before
• Verify the terminal connects and allows command execution
• Unit tests pass (npx vitest run src/components/pod/Details.test.tsx)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: justinas-wix
Once this PR has been reviewed and has the lgtm label, please assign ashu8912 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[justinas-wix]

Sorry I have messed up previous PR with squashing to much and then force pushing on top...

• Opened new one instead to make history clean.
• Added tests please review when you have time.

Appreciated!!!