Let a project be removed from the launcher

[ntatschner]

You couldn't remove a project from the launcher, and loadout project remove didn't really remove one either.

What was wrong

The project list is read from the shared workspace registry. loadout project remove x without --from-workspace only forgets this machine's path, so the project stayed on the list, marked "not on this machine", while the command printed Removed x and exited 0. Reproduced in a sandboxed home:

--- remove
Removed repo (the repository itself was not touched)
exit 0
--- list after
      Project   Agent    Location
      repo      claude   not on this machine

The launcher screen had no remove at all. The teams screen and the manager both have one.

What this changes

• Launcher: Delete on the project list, or Registry > Remove the selected project…, asks first and then runs project remove <slug> --from-workspace --non-interactive through the same parser as the command line. It removes from the workspace because that's what taking it off the list means. The question says this reaches every machine sharing the workspace, and that the repository, instructions and memory aren't touched. Delete is bound to the list only, so it still deletes characters in the filter. It's also listed on the ? panel.
• Command line: a removal without --from-workspace now says what actually happened: it forgot where the project is on this machine, the project is still in the shared registry and so still listed, and here's the --from-workspace command. The behaviour hasn't changed; only the report was wrong.

Evidence

• Full suite on origin/main plus this change: 3338 passed, 0 failed, 22 skipped.
• LauncherRemoveTests presses the real keys. ProjectRemoveContractTests runs the built CLI and checks project list --json afterwards.
• Each new test fails under a mutation: removing the binding, ignoring the answer, restoring the old wording.
• A test checking that Delete in the filter doesn't remove was dropped. The text field consumes Delete before any window binding, so it passed even with the key bound window-wide.

Not verified

• The confirmation dialog itself. As on the teams screen, a dialog waiting on a keypress can't be driven headlessly; the tests inject the answer.
• Delete in a real Windows console.