Upgrade the versions of astroid and dill

[Pierre-Sassoulas]

Type of Changes

	Type
✓	🔨 Refactoring

Description

Make sure that we use the real version of dill on all interpreter now that dill released version 0.3.6. also explicitly use the latest astroid.

[Pierre-Sassoulas]

Wow, I'm really sorry about the ping of every code owner, isort and pre-commit suddenly started to modify all the files for no apparent reason. (Edit : I added "dill<0.2 without closing quote in the pyproject.toml with catastrophic result, meaxima culpa 💦 )

[coveralls]

Pull Request Test Coverage Report for Build 3543136614

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.005%) to 95.422%

---

Files with Coverage Reduction	New Missed Lines	%
pylint/checkers/classes/class_checker.py	1	94.69%

Totals
Change from base Build 3543069842:	-0.005%
Covered Lines:	17549
Relevant Lines:	18391

---

💛 - Coveralls

[github-actions]

🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉

This comment was generated for commit 4c8cce7

[DudeNr33]

Shouldn't we keep the >=0.3.6 constraint at least for Python >= 3.11 if lower versions cause problems?

[Pierre-Sassoulas]

This should be enforced by pip and dill's metadata automatically.

[DanielNoord]

I was thinking the same but Pierre is right, that shouldn't be our responsibility.

[Pierre-Sassoulas]

Suggested change

	"dill>=0.2",
	"dill>=0.2,<1",

Following pyflake's 3.0 release all old releases of autoflake now have broken 2.X typing support. Let's do better for pylint :)
Edit: It's better if I open another issue for this though.

[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-7838-to-maintenance/2.15.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 15733b4c8117e19e57e60a003e693ca2a5c494a7
# Push it to GitHub
git push --set-upstream origin backport-7838-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-7838-to-maintenance/2.15.x.