Correct pre-commit's pylint warnings

[crazybolillo]

The introduction of use-yield-from generated a new warning on the source code. Some messages no longer needed to be disabled as well. These warnings have been corrected to prevent pre-commit from failing.

Type of Changes

	Type
✓	🔨 Refactoring

[Pierre-Sassoulas]

Thank you @crazybolillo. I fixed that elsewhere (pytest cov bump). But there's still thé pypy 3.10 segfault. Might just merge despite the segfault.

[Pierre-Sassoulas]

Nvm, upgrading stealthily like I did is bad practice.

[crazybolillo]

Seemed suspiciously easy. Now I am not so sure about my changes since it seems like the CI complains about the non-iterable while my local environment did not. Probably better to focus our efforts on your PR. I have not read much about the segfault you mention but I will see if I can be of any help.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.76%. Comparing base (de942f3) to head (5d55b26).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2407   +/-   ##
=======================================
  Coverage   92.75%   92.76%           
=======================================
  Files          94       94           
  Lines       11088    11087    -1     
=======================================
  Hits        10285    10285           
+ Misses        803      802    -1     

Flag	Coverage Δ
linux	92.57% <100.00%> (+<0.01%)	⬆️
pypy	90.77% <0.00%> (+<0.01%)	⬆️
windows	92.36% <0.00%> (+<0.01%)	⬆️

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

Files	Coverage Δ
astroid/manager.py	89.53% <100.00%> (+0.37%)	⬆️

[Pierre-Sassoulas]

Well the segfault is ever flaky or went in of order 😄

[Pierre-Sassoulas]

Thanks again @crazybolillo . Also yes, often the astroid's local need to be regenerated from scratch. Or we might have some skip to add on some tests.