"Check if generated files are up to date" job misses regen-unicodedata and regen-limited-abi

[sobolevn]

Feature or enhancement

Currently our regen-all is missing several regen- targets:

@echo "Note: make regen-stdlib-module-names, make regen-limited-abi, "
@echo "make regen-configure, make regen-sbom, and make regen-unicodedata should be run manually"

While our CI job to check regenerated files does not check them:

cpython/.github/workflows/build.yml

Lines 120 to 124 in 2a6b6b3

	- name: Build CPython
	run: |
	make -j4 regen-all
	make regen-stdlib-module-names regen-sbom
	- name: Check for changes

This does not seem right, I think that we should add:

• make regen-unicodedata (it requires internet access, but GitHub jobs always have access, see gh-96954: Don't run regen-unicodedata in regen-all #112120)
• make regen-limited-abi (needs to compile python to get the ABI)

How long does it work? Testing locally first:

make regen-unicodedata  9.44s user 0.47s system 27% cpu 35.719 total
make regen-limited-abi  2.35s user 0.76s system 77% cpu 4.019 total (with pre-existing cache)

I propose adding these two make targets to the test to be extra safe.
What do others think? :)
If agreed, I will send a PR.

Linked PRs

• gh-126524: Run regen-unicodedata as a part of our CI #126682

[sobolevn]

I don't touch regen-configure here, because it will require a different solution, will create a new issue about it later.

[encukou]

There's no need to add regen-limited-abi, since the CI runs make check-limited-abi.
That checks that regen-limited-abi wouldn't make changes, and tries to generate a nicer message than you'd get just by comparing the resulting diff.

[sobolevn]

When I add make regen-unicodedata here's how the CI speed changes:

• Before: 1m 59s https://github.com/python/cpython/actions/runs/11717879421/job/32638269138?pr=126526
• After: 2m 11s https://github.com/python/cpython/actions/runs/11777998050/job/32803523310?pr=126682

Does not seem like it is slow now.