frontend: Implement new Activity feature for tabs and windows

[sniok]

This PR adds new Activity concept, allowing users to manage terminals, logs, and tasks outside of a details view.
It's a generic system for opening new tabs/window, resizing them, minimizing.
This replaces drawer mode.

You create a new activity by calling

Activity.launch({
  id: "some-id",
  content: <div>content</div>,
  location: "split-right",
});

All activities are stored in the activitySlice redux store.

Settings were updated

Related Issue

Fixes #3486 #3419

Steps to Test

1. Open resource details
2. Open terminals
3. Open logs
4. Open Edit dialogs
5. Open Create new resource dialog

Testing done

1. Manual testing
2. a11y Axe check
3. Fastpass a11y check

[Copilot]

Pull Request Overview

Introduces a generic Activity system for managing UI panels as tabs/windows and replaces the old detail-drawer mode throughout the frontend.

• Registers the new activityReducer in the root Redux reducer and ports stream calls to include cluster context.
• Adds Activity.launch, Activity.update, and Activity.close calls across components (pods, editors, logs, search links, etc.).
• Updates i18n keys for new UI options (“Window”, “Full page”, “Overview”) and removes old “Overlay” drawer toggle.

Reviewed Changes

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

File	Description
frontend/src/redux/reducers/reducers.tsx	Adds activity slice to combined reducers
frontend/src/components/common/Resource/CreateButton.tsx	Replaces dialog-state with Activity.launch for creation
frontend/src/i18n/locales/zh/translation.json (and other locales)	Adds keys for new Activity modes and removes “Overlay”

Comments suppressed due to low confidence (1)

frontend/src/i18n/locales/zh/translation.json:12

• The translation value for "Window" is empty; please provide the proper Chinese translation to ensure localization completeness.

  "Overview": "概览",

[joaquimrocha]

I like that you used the icon for different resources and it looks nice, but seems redundant when we have the name repeated? Maybe something to handle later.

[joaquimrocha]

Oops, clicked submit too early. One sec.

[joaquimrocha]

Great job @sniok ! It does bring Headlamp to another level of productivity.
Please do check my comments in some of the code.

Here are also some issues I found during testing:

1. The Node Shell doesn't use the windowed rendering
2. In the map view, the taskbar covers the map zoom lower side buttons
3. I wonder how discoverable the snapping left/right is. Would it work if we added snap-left/snap-right/maximize buttons to the right of the drag-::: handle? Leaving only the minizime + close button to the right? (maybe it looks bad, just throwing out ideas)

[yolossn]

Hey, this looks great, really intuitive and smooth overall.I wanted to share a few issues and thoughts I encountered during testing:

It will be good have an option to close the tabs from the overview

I noticed a few rendering issues when multiple tabs were open:

1. When switching between two tabs the activity bar moved up and down based on the tab that was selected

Activity.tab.render.issue.mov

2. When multiple logs, exec and detail tabs were open the logs on the right side started bleeding out of the tab.

Activity.Tab.issue.2.mov

The tabs are missing Cluster contexts

1. When tabs from multiple clusters are open the tabs dont display which cluster they belong to.

Cluster.Context.missing.in.tabs.mov

2. Also, if a user is viewing two tabs from different clusters (say A and B) and is currently in the context of cluster B, all links, even from the tab that belongs to cluster A, direct to cluster B.

Cluster.Context.issue.with.Links.in.details.tab.mov

[joaquimrocha]

Wow! Great findings @yolossn ! Thank you!

[joaquimrocha]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joaquimrocha, sniok

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [joaquimrocha,sniok]

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