docs: point ADR-0077's recovery message at the write lease

[newhoggy]

Summary

• Since Drive write lease Phase 3 (part 2): require --lease on every Sheets/Docs write verb #1670, --lease is required on every Sheets/Docs write verb (including the four SheetsDelete ones), and drive lease acquire already backs the file up before the write — so ADR-0077 §5's "there is still no recovery path but Drive's own version history" no longer holds.
• Updates the runtime recovery message (structure.rs's RECOVERY_NOTE, its DeleteSheetCommand doc comment) and docs/drive.md's example output to point at the lease's own backup first, falling back to Drive's version history.
• Updates ADR-0080's Status and Consequences sections, which already tracked this as a pending supersession ("will supersede ADR-0077 §5 ... once Phase 3 below lands — not yet"), to reflect that it has now landed.
• ADR-0077 itself is left untouched — matches this codebase's existing convention (see ADR-0075/ADR-0077) of a newer ADR documenting what it changes about an older one, rather than editing an accepted ADR in place.
• The message still points at the Drive UI for the actual restore, since drive lease restore (Phase 4) hasn't landed yet.

Test plan

• cargo test --lib — full suite (9330 passed)
• cargo clippy --all-targets -- -D warnings
• cargo fmt --check
• Updated the one test asserting on the old message text (describe_lines/describe for delete-sheet) to match the new wording

[github-actions]

Coverage

Total: 97.24% ⚪ 0 pp vs main

Comparing b870d4f..97076db (merge-base → PR head)

No per-file coverage changes vs main.

Patch coverage

Patch: 100% (2/2 new lines covered)

File	Patch	Uncovered new lines
src/drive/sheets/structure.rs	100% (2/2)	—

_{📦 Full per-file coverage summary · run summary}