fix: skip escrow orphan recovery under automated UI tests

[arzafran]

What this does

Fixes the red `ui-regressions` job on main. Every app launch in a UI test run was opening with the previous launch's terminals as extra workspaces (2, then 10, then 20), so the close-window and close-workspace tests saw the wrong workspace count and the release never ran.

Each launch leaves its shells escrowed when the test kills it, and the next launch's orphan recovery revived them. Snapshot restore already skips automated runs; orphan recovery now follows the same rule (`SessionRestorePolicy.isRunningUnderAutomatedTests`, DEBUG only). Real users and the relaunch recovery socket test, which strips the UI test variables, are unaffected.

These tests were not failing because of a recent change. `ui-regressions` only started running them in 9255c64.

Two more tests in the same job were broken before this branch:

• testCtrlDAfterClosingBottomRowIn2x2KeepsWorkspaceOpen: its harness asked for a fifth pane, over the four-pane limit, so setup always failed. It now reuses the existing right column.
• CloseWindowConfirmDialogUITests is removed. It asserted that closing a window keeps its shell running for reopen. Closing a window now confirms and then frees its sessions, and WindowCloseConfirmCancelUITests covers that.

Test plan

• `test-e2e` passes for `CloseWorkspaceCmdDUITests` on macos-26 against this branch
• `test-e2e` passes for `CloseWindowConfirmDialogUITests`, `CloseWorkspaceConfirmDialogUITests` and `CloseWorkspacesConfirmDialogUITests`
• PR CI is green