Resolve some test warnings

[berland]

Issue
Resolves noise in pytest output from expected warnings

Approach
Assert or ignore each warning

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure unit tests pass locally after every commit (git rebase -i main --exec 'just rapid-tests')

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Add backport label to latest release (format: 'backport release-branch-name')

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.60%. Comparing base (d553866) to head (964b8bd).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12562      +/-   ##
==========================================
- Coverage   90.62%   90.60%   -0.02%     
==========================================
  Files         432      432              
  Lines       29738    29738              
==========================================
- Hits        26949    26945       -4     
- Misses       2789     2793       +4     

Flag	Coverage Δ
cli-tests	37.59% <ø> (ø)
gui-tests	68.70% <ø> (+0.01%)	⬆️
performance-and-unit-tests	74.12% <ø> (-0.02%)	⬇️
test	38.32% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[codspeed-hq]

CodSpeed Performance Report

Merging #12562 will not alter performance

_{Comparing berland:resolve_warnings (964b8bd) with main (d553866)}

Summary

✅ 22 untouched