fix: restore Ctrl+C interrupts and prepare v1.0.2

[HelloThisWorld]

Summary

• Reserve Ctrl+C for terminal interrupt input instead of copying.
• Keep Ctrl+Shift+C for copy and migrate the legacy generated Ctrl+C copy binding from existing user settings.
• Document and regression-test the default right-click copy-then-paste workflow.
• Prepare an immutable self-signed v1.0.2 patch release without replacing the existing v1.0.1 Release or assets.

Related issues

None.

Detailed changes

• Remove the Ctrl+C copy entry from winTerm user defaults.
• Skip the legacy exact Ctrl+C copy binding while loading user settings, mark the settings for persistence, and leave other key bindings unchanged.
• Add settings-model and terminal-control regression coverage.
• Add detailed keyboard, mouse, clipboard, paste-warning, and VT mouse-reporting instructions to the README.
• Update the package, module, release workflow, WinGet workflow, release metadata, support policy, security policy, changelog, and release notes to 1.0.2.
• Keep Workspace Schema 2, Docking Model 1, Shell Protocol 1, and Theme Schema 1 unchanged.

Validation performed

• Windows PowerShell 5.1 on Windows 11 x64:
  • powershell.exe -NoLogo -NoProfile -ExecutionPolicy Bypass -File scripts/winterm/test.ps1 -Suite Smoke
  • Result: passed, including PowerShell syntax, version consistency, release workflow boundaries, branding, Ctrl+C reservation, right-click behavior, workspaces, diagnostics, and privacy checks.
• git diff --check
  • Result: passed.
• Compiled C++ unit tests were not available locally because this host does not have the required Visual Studio/MSBuild toolchain; GitHub Actions will run the native Windows build and tests.

Checklist

• The change is focused and does not include unrelated formatting.
• Tests were added or updated where appropriate.
• All tests claimed above actually ran and passed.
• User-facing behavior and limitations are documented in this repository.
• Version or schema changes include compatibility and migration notes.
• Package identity, winterm.exe, and Microsoft Terminal coexistence remain isolated.
• No command text, terminal output, clipboard content, credentials, or private paths are logged.
• New source and script files contain the appropriate MIT license header.
• I did not include generated build output, secrets, certificates, or local absolute paths.