Use std::assert_matches! in tests (#641)

[octoaide]

This PR converts test-only occurrences of assert!(matches!(...))
to the std::assert_matches! macro where it is safe and clearer.

Summary of changes

• Converted 8 assertions total:
  • src/bin/roxyd/control.rs: 7 assertions
  • src/bin/roxyd/handlers/hostname.rs: 1 assertion
• Removed 4 redundant debug-value messages that duplicated the
  same {value:?} output without adding context.
• No assertions were deferred; all converted values present safe
  Debug output and do not expose secrets or sensitive payloads.

Why
Using std::assert_matches! improves test diagnostics and intent
compared to assert!(matches!(...)) and makes failure messages
clearer when a match fails.

Verification

• cargo test --all-features passed
• cargo clippy --tests --all-features -- -D warnings passed
• Changes are test-only and do not affect runtime behavior

Related

• Issue: Use assert_matches! in tests #641

Closes #641

[codecov]

Codecov Report

❌ Patch coverage is 50.00000% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 81.92%. Comparing base (bd613ab) to head (ec0c788).

Files with missing lines	Patch %	Lines
src/bin/roxyd/control.rs	42.85%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #642      +/-   ##
==========================================
- Coverage   82.02%   81.92%   -0.10%     
==========================================
  Files          27       27              
  Lines        4261     4261              
==========================================
- Hits         3495     3491       -4     
- Misses        766      770       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[zmrdltl]

Please simplify the path by consolidating std into a single one.

[octoaide]

I reviewed the feedback and made the requested simplifications to the std paths in the test modules.

What I changed

• Consolidated std::assert_matches! into a single use std::assert_matches; (or added assert_matches to the existing use std::{...}) in the test modules.
• src/bin/roxyd/control.rs
  • Added assert_matches to the test use std::{...} block and replaced 7 occurrences of std::assert_matches! with assert_matches!.
• src/bin/roxyd/handlers/hostname.rs
  • Added use std::assert_matches; to the test module and replaced the std::assert_matches! calls with assert_matches!.

Verification

• I committed and pushed the changes.
• Ran cargo test --all-features — all 182 tests passed.
• Ran cargo clippy --tests --all-features -- -D warnings — no warnings.

About the Codecov comment

• Codecov reports 4 missing lines in src/bin/roxyd/control.rs (patch coverage on the changed lines). Those are test assertion lines affected by this test-only refactor; no production logic was changed. The Codecov note is informational and doesn’t indicate a functional regression.

Thanks for the review — the path consolidation request is implemented and verified.