Release prep v32.0.5rc3

[AyanSinhaMahapatra]

Reference: #3435

Tasks

• Reviewed contribution guidelines
• PR is descriptively titled 📑 and links the original issue above 🔗
• Tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR
  Run tests locally to check for errors.
• Commits are in uniquely-named feature branch and has no merge conflicts 📁
• Looked for possible updates in documentation and added updates if applicable
• Updated CHANGELOG.rst

[AyanSinhaMahapatra]

Release tests now pass at https://github.com/AyanSinhaMahapatra/scancode-toolkit/actions/runs/5356158796
All green!

[pombredanne]

LGTM!
Keep in mind to eventually merge all the RC changelog entries in one for 32.0.5
Also I wonder if we need so many RCs for a minor dot release

[AyanSinhaMahapatra]

Thanks @pombredanne

Keep in mind to eventually merge all the RC changelog entries in one for 32.0.5

Sure, I'll do that. The rc2 and rc3 are minor though, without any material changes.

Also I wonder if we need so many RCs for a minor dot release

The first RC had was created because we merged the license detections and improvements branch. This failed with the pypi upload limit bug, but this already had published a pypi release with the source archive as it was under the limit. So it would have been problematic to yank from pypi, delete the github release, and then also force push the tag.
Second time we did not change anything in code, just bump after the new pypi limit was approved. So I did not test the release scripts again because there was no code changes (my bad, should have done a check anyway, it failed because of other changes). Here I did not want to delete the tag and force push it again as it was there for more than a day as I was trying to figure out the issue. If it was not much time I'd have fixed and force-pushed the tag allright.
That is why we have 3 rcs for a dot release which should not have happened ideally. 😅

Merging thanks!