test(renderer): explicit budgets for the remaining full-App edge tests

[PeterGuy326]

Preflight

• Searched open and closed PRs for related changes (follows test(renderer): give the full-App toolbar test an explicit 15s budget #531, which gave the toolbar test the same treatment; ci(renderer): App context navigation toolbar test times out on fresh runs of main (both platforms) #529 tracks the family).
• No credentials, personal data, private paths, or private screenshots.
• Test-only change on top of main @ ed94fca.

Summary

After the toolbar test got its explicit 15s budget (#531), the next-slowest tests surfaced at the 5s vitest default on macOS runners. This gives the three observed edge-dwellers the same explicit 15s budget the other heavy tests in these files already carry:

Test	Observed timeouts
App.test.tsx > reanchors a repeated project turn link…	4 consecutive runs across #527/#522/#513 (deterministic on macOS)
App.test.tsx > binds the ready %s runtime in HireDrawer…	1 run (#522, job 109243787847)
docs-lifecycle.test.tsx > preserves undo and redo history…	1 run (#522, job 109243787847)

No production code changes; test files only.

Evidence

• All three failures are Test timed out in 5000ms (job logs 109243787847, 109247014992, 109247113086), each followed by a green rerun or a pass on the other platform — the signature of cold, heavy tests at the 5s edge under runner load, not hangs.
• The reanchors case timed out on every macOS run observed today (4/4), so it sits furthest above the default.

Assumptions

• These tests are slow, not hung. If any of them exhausts the 15s budget on CI, that points at a genuine hang and needs the direction-2 investigation from ci(renderer): App context navigation toolbar test times out on fresh runs of main (both platforms) #529 instead of a larger budget.

Acceptance

• Node 24 / ubuntu-latest and Node 24 / macos-14 pass on this PR and on fresh runs of main after merge.
• No production code change: test files only.

Refs #529, #531