docs: clarify that process exclusions affect working sets only

[MataM15]

Summary

Clarify the actual scope of process exclusions in the UI, all 30 localizations, and README. This independent contribution is based on upstream main; candidate commit: df18c58.

Related Issue

Related to #176, where the distinction between process exclusions and global memory cleanups was explained. This PR documents that distinction rather than changing the cleanup behavior.

Changes

• Rename the exclusion heading to make the working-set scope explicit.
• Add a localized explanation and its model property/main-window binding in all 30 supported languages.
• State that exclusions do not prevent global memory cleanups or pause automatic optimization.
• Remove the broader protection claim from the README feature description.

Checklist

• My code follows the project’s coding style and conventions.
• I have tested the changes locally.
• I have updated documentation if necessary.
• This PR does not introduce any breaking changes.
• I have added unit tests if applicable. No behavior changes; localization contract validation is linked below.

Additional Notes

Standalone hosted Windows validation: Release/WPF build with 0 warnings and 0 errors; all 30 localization JSON files passed duplicate-key, model-key-set, and nonempty-string checks against the 74 localization members. The final log summary has a stale build label, but the preceding restore and WPF build steps executed successfully.

Native-speaker review and visual confirmation are still welcome; structural checks do not replace those. No cleanup logic, resizing implementation, benchmark, or fork-only CI tooling is included. Scope: 33 files, 115 changed lines.