CI: Temporarily skip paths with spaces to avoid error

[hugovk]

PRs like these:

• gh-105071: add PyUnstable_Exc_PrepReraiseStar to expose except* implementation in the unstable API #105072
• gh-105107: Remove PyEval_CallFunction() function #105108

Have NEWS files in subdirectories containing spaces:

• Misc/NEWS.d/next/C API/2023-05-30-10-15-13.gh-issue-105071.dPtp7c.rst
• Misc/NEWS.d/next/C API/2023-05-30-19-11-09.gh-issue-105107.YQwMnm.rst

But the https://github.com/Ana06/get-changed-files action (added in #103914) fails for such files with:

Error: One of your files includes a space. Consider using a different output format or removing spaces from your filenames. Please submit an issue on this action's GitHub repo.

We ran into this before and worked around it in #103019 by skipping Misc and its subdirs.

Let's do something similar here, by replacing Misc with a list of its subdirs that are absent a space.

---

See also python/core-workflow#186 to rename the C API and Core and Builtins directories to C-API and Core-and-Builtins to avoid this altogether.

[hugovk]

✅ No error with a dummy file at Misc/NEWS.d/next/C API/2023-05-30-21-34-29.gh-issue-105107.1mmbfA.rst (05cd028):

Run Ana06/get-changed-files@v2.2.0 Base commit: 457[1](https://github.com/python/cpython/actions/runs/5125091879/jobs/9217804839#step:5:1)eedca2f70768ddc4a2fd4fba2ae11b4c8037 Head commit: 05cd028fd4c56e3173b134b10dc947c3af471d82 All: Added: Modified: Removed: Renamed: Added or modified: Added, modified or renamed: 

https://github.com/python/cpython/actions/runs/5125091879/jobs/9217804839

[vstinner]

But the https://github.com/Ana06/get-changed-files action (added in #103914) fails for such files with

Maybe you should report the bug there?

[hugovk]

It's a feature: https://github.com/Ana06/get-changed-files#usage says the default behaviour is to return files separated by spaces (format: 'space-delimited'), and will fail if any files contain spaces. They suggest using one of the other formats in such case (CSV, JSON).

(Let's continue discussion in #103914).

[webknjaz]

@vstinner I've just submitted a proper fix: #105151