Enable 3.11 in the CI

[DanielNoord]

]

Steps

• Write a good description on what the PR does.

Description

Type of Changes

	Type
✓	🔨 Refactoring

Related Issue

Ref. #1516

[coveralls]

Pull Request Test Coverage Report for Build 2206945525

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 30 unchanged lines in 1 file lost coverage.
• Overall coverage remained the same at 91.502%

---

Files with Coverage Reduction	New Missed Lines	%
astroid/brain/brain_gi.py	30	23.02%

Totals
Change from base Build 2173689786:	0.0%
Covered Lines:	9088
Relevant Lines:	9932

---

💛 - Coveralls

[cdce8p]

Python 3.11 is still in alpha at this time. Maybe it's better to add it as a separate job for now, instead of using always(). We can merge that back once the beta has gotten stable enough.

[DanielNoord]

@cdce8p This remains necessary for the coverage to include 3.11 which would be good for any changes we introduce to fix regression with that version. I have removed it from the windows job though.

[cdce8p]

Not sure that is all that useful. The coverage is merged anyway, so the only thing we would get would be the lines with PY311_PLUS.

[DanielNoord]

I think that would still be helpful. For example, more "risky" PRs such as #1513 would probably be less risky if we know coverage is okay.

[cdce8p]

Not sure that is all that useful. The coverage is merged anyway, so the only thing we would get would be the lines with PY311_PLUS.

[cdce8p]

Do we want / need to test Windows? For almost everything the Linux test should be enough. Once merged we'll test Windows anyway.

[cdce8p]

Pushed some minor changes. Looks good now!