Redesign project dev wizard + tabs for a more interactive, guided flow (MVP.1)

[lasomethingsomething]

User story

Note: This is additive to #1009 and iterates upon what's been shipped already: install flow, dashboard, logs, watchers.

User story

As a dev using project dev, I want one always-visible overview with an interactive checklist and inline explanations, so that I always know where I am and what the CLI is doing, without editing config or memorizing commands.

Principles:

• get me where I need to go in a quick, non-intrusive way
• give me one checklist that serves both install and migration (sets you up with Docker), and a clear choice between install and migration
• give me an interactive checklist inside an always-visible overview
• make sure that every step also runs via flags

A) Setup wizard ("Set up Docker development environment")

The migration path for projects that aren't dev-ready with the Docker setup. Bootstraps the Docker dev config (.shopware-project.yml), and hands off to the dashboard. The CLI detects the project state; user doesn't choose it.

Overarching (whole flow)

• Remove "step 1/3" counter from migration wizard steps. Remove steps badge from migration wizard view #1153

B) Tabs

User is able to solve a problem on every tab and understands clearly what they can do/solve and how to do it. For now these tabs will be largely informational and lean toward diagnostic.

Overview tab (rename from "General")

Core problem it solves: helps user to understand current status, what actions are available, and how to start, stop, change status, or take action.

• See new (July 1) design, folding Config Tab functionality into this tab. Incorporate missing features.

Instance tab

• Rename "Scroll" toggle to "Scroll log"
• Rename "Follow" toggle to "Follow log"
• Bug? After running through the list I tried to come back to Admin Watcher and couldn't.

Acceptance criteria

• At all times the user can see progress, project state, health, and the command being actioned.
• Every redesigned step runs headless via flags (verified for CI/agent use).
• No regressions to the already-shipped install flow, dashboard, logs, or watchers from New Development Workflow using Docker + shopware-cli #1009.
• User events metric points confirmed and collection in place.
• Documentation written. feat(cli): document new Docker-based development environment docs#2286
• Tests added or adjusted accordingly.
• Every step runs headless as well via flags (CI / agents).

[Weltraumakustik]

Arnold Stoba (@arnoldstoba) would you please do a quick review from UX Engineering perspective on this? Maybe there's additional ideas or optimizations

[lasomethingsomething]

Soner (@shyim) Tomasz Turkowski (@tturkowski) As discussed/agreed upon in our standup, our parameters for TUI sizing:

• 80 columns wide x 24 rows tall is the floor
• If we design for/target 120 columns wide x 40 rows tall, we accommodate the work we've done so far, without needing scroll.
• Vertical flex is an option used by lazygit (the TUI I'm most familiar with) and achievable with charm.land tooling, though you wire it yourself
• stickers allows us to set ratios instead of computing individual pane size by hand

If you have any second thoughts, of course we can discuss :)