test: stabilize settings terminal tests and the macOS config path check

[srothgan]

Summary

• Add wait_settings_ready to the terminal test harness and use it in all six tests that open settings, so the first edit key is sent only after the open-time settings refresh has finished.
• Add wait_settings_saved and use it in the hook and permission tests, so the final Esc is sent only after the acknowledged save has closed its editor.
• Compare canonical paths for the local settings file in config_commands_inspect_only_the_selected_profile.

Test-only change; no production code is touched.

Why

Settings ignore edit keys while a settings request is pending, and the tests sent keys without waiting for that request to finish.

• Test Ubuntu failed on chore(deps-dev): bump jscpd from 5.3.2 to 5.4.0 in the npm-minor-patch group across 1 directory #417: guided_hook_creation_survives_resize_and_saves_a_complete_hook_with_existing_data timed out waiting for streamed line 8. The final Esc arrived between mutate_setting and settings_result, was dropped by the editor, and the test stayed in settings. The fixture writes the settings file before it sends the result, so waiting for the persisted file did not cover this.
• The same unsynchronized pattern existed at the other places these tests open settings or leave an editor after a save. fix: restore scrollback across resizes and stabilize CI tests #422 fixed only the open-time case in the hook test.
• The Nightly run on main (https://github.com/srothgan/claude-code-rust/actions/runs/37382537914) failed Test (macos-latest) at tests/claude_config_dir.rs:37: the command reports the local settings path from the resolved working directory (/private/var/...) while the test compared it with the unresolved temporary path (/var/...). The test was added in fix(tui): reconcile terminal size before inline redraws #408 and had not run on macOS before.

Validation

• Automated: cargo fmt --all -- --check, cargo clippy --all-targets --all-features -- -D warnings, cargo test --locked --all-features --test claude_config_dir (3 passed), and the six changed tests in cargo test --locked --all-features --test terminal_resize -- --test-threads=1 (6 passed), all on Windows. The full cargo test --all-features suite was not run locally.
• Manual: None. The races did not reproduce locally before the change, and the macOS path case cannot run on Windows, so CI on Ubuntu and macOS is the real check. The full suite on macOS only runs in Nightly.
• Screenshot/video (if UI changed): N/A

Notes

• Breaking changes: N/A
• Docs updated: N/A
• Governance/release impact: N/A
• The Nightly macOS job stopped at claude_config_dir, so the test binaries after it have not run on macOS in the full suite since fix(tui): reconcile terminal size before inline redraws #408. Further macOS-only failures may surface once this one is fixed.