Test on PyPy 3.10

[jacobtylerwalls]

Type of Changes

	Type
✓	🔨 Refactoring

Description

CI is failing on main and all PRs because pytest can't run on the newest PyPy 3.9 image. When the image came out, 3.10 also became available for the first time.

Let's just run on 3.10 to unblock CI. Two PyPy versions is fine?

[codecov]

Codecov Report

Merging #2222 (e0f2d82) into main (842548d) will increase coverage by 0.02%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2222      +/-   ##
==========================================
+ Coverage   92.80%   92.82%   +0.02%     
==========================================
  Files          94       94              
  Lines       10840    10836       -4     
==========================================
- Hits        10060    10059       -1     
+ Misses        780      777       -3     

Flag	Coverage Δ
linux	92.63% <100.00%> (+0.07%)	⬆️
pypy	91.25% <100.00%> (+3.17%)	⬆️
windows	92.42% <100.00%> (+0.02%)	⬆️

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

Impacted Files	Coverage Δ
astroid/nodes/node_classes.py	95.46% <100.00%> (+0.19%)	⬆️

... and 3 files with indirect coverage changes

[github-actions]

The backport to maintenance/2.15.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-maintenance/2.15.x maintenance/2.15.x
# Navigate to the new working tree
cd .worktrees/backport-maintenance/2.15.x
# Create a new branch
git switch --create backport-2222-to-maintenance/2.15.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 efb34f2b84c9f019ffceacef3448d8351563b6a2
# Push it to GitHub
git push --set-upstream origin backport-2222-to-maintenance/2.15.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-maintenance/2.15.x

Then, create a pull request where the base branch is maintenance/2.15.x and the compare/head branch is backport-2222-to-maintenance/2.15.x.

[jacobtylerwalls]

@DanielNoord I was able to resolve the underlying issue with PyPy 3.9 by deleting the cached image from each project's Actions environment.

So I'll avoid backporting this or doing the same in pylint.

Still, I think it's okay to just test on lowest and highest in astroid for now.