Strengthen the Logger functional coverage and stabilize slow-runner steps

Problem/Motivation

The Logger sub-module's functional scenarios assert widget presence rather than behavior (saved values, validator messages, the forwarded record's content), the PSR-3-only mode has no browser-level coverage, and several suite runs on shared CI runners have failed on a single form-submit step exceeding the 90s step timeout while the same suite passes locally and on retry.

Proposed resolution

Split the Logger feature into a forwarding feature and a settings feature; pin assertions to real strings (the saved-configuration message, the channel validator text, the forwarded message in the database log); add an end-to-end PSR-3-only scenario that restores hybrid mode; add a scan-all-matches negative assertion step; raise the default step timeout for slow shared runners; ignore the failure-dump HTML files.

Remaining tasks

• ✅ File an issue
• ❌ Addition/Change/Update/Fix
• ❌ Testing to ensure no regression
• ❌ Automated unit/functional testing coverage
• ➖ Developer Documentation support
• ➖ User Guide Documentation support
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ❌ Reviewed by a human
• ❌ Code review by maintainers
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ✅ Update Release Notes
• ✅ Release admin_audit_trail-1.0.11

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• N/A (test-only change)