Bump astroid to 3.0.2, update changelog

[jacobtylerwalls]

What's New in astroid 3.0.2?

Release date: 2023-12-12

• Avoid duplicate inference results for some uses of typing.X constructs like
  Tuple[Optional[int], ...]. This was causing pylint to occasionally omit
  messages like deprecated-typing-alias.
  Closes [primer noise] deprecated-typing-alias pylint#9220

[codecov]

Codecov Report

Merging #2343 (4cf579a) into maintenance/3.0.x (958ce1e) will increase coverage by 0.00%.
Report is 6 commits behind head on maintenance/3.0.x.
The diff coverage is 100.00%.

Additional details and impacted files

@@                Coverage Diff                 @@
##           maintenance/3.0.x    #2343   +/-   ##
==================================================
  Coverage              92.85%   92.86%           
==================================================
  Files                     94       94           
  Lines                  11056    11068   +12     
==================================================
+ Hits                   10266    10278   +12     
  Misses                   790      790           

Flag	Coverage Δ
linux	92.67% <100.00%> (+<0.01%)	⬆️
pypy	91.00% <92.30%> (+<0.01%)	⬆️
windows	92.45% <100.00%> (+<0.01%)	⬆️

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

Files	Coverage Δ
astroid/__pkginfo__.py	100.00% <100.00%> (ø)
astroid/brain/brain_typing.py	87.17% <100.00%> (+0.16%)	⬆️
astroid/const.py	100.00% <100.00%> (ø)
astroid/nodes/node_classes.py	94.83% <100.00%> (+0.01%)	⬆️
astroid/protocols.py	90.28% <100.00%> (+0.06%)	⬆️

[jacobtylerwalls]

Don't worry; the tagged 3.0.1 went out with this correctly as 3.0.1. This was a mistake where instead of amending the merge commit to main, I added a commit to the maintenance branch as discussed here

[Pierre-Sassoulas]

Shouldn't this be two commits one with each version then we rebase ? Approving because you probably also thougth of something that work :)

[jacobtylerwalls]

The mistake already happened two months ago. There shouldn't have been "3.1.0-dev0" on this branch at all, so this squash merge will fix a bug. You might be thinking of going from 3.0.2 -> 3.1.0-dev0 on the main branch.