Diagnose remaining NumPy 3.14 failure

[FlorianPfaff]

Temporary diagnostic PR based on #4293. It runs the NumPy 3.14 suite with --maxfail=1 and always uploads the traceback/JUnit artifact. No production changes beyond the #4293 fixes are proposed.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ COPYPASTE	jscpd	yes		no	no	23.36s
✅ JSON	prettier	7	0	0	0	1.11s
✅ JSON	v8r	7		0	0	3.27s
✅ MARKDOWN	markdownlint	68	0	0	0	2.1s
✅ MARKDOWN	markdown-table-formatter	68	0	0	0	0.8s
✅ PYTHON	black	1489	180	0	0	95.04s
✅ PYTHON	isort	1489	325	0	0	2.59s
✅ REPOSITORY	betterleaks	yes		no	no	2.53s
✅ REPOSITORY	checkov	yes		no	no	56.65s
✅ REPOSITORY	gitleaks	yes		no	no	15.69s
✅ REPOSITORY	git_diff	yes		no	no	0.36s
✅ REPOSITORY	secretlint	yes		no	no	58.23s
✅ REPOSITORY	syft	yes		no	no	6.02s
✅ REPOSITORY	trivy-sbom	yes		no	no	7.36s
✅ REPOSITORY	trufflehog	yes		no	no	31.9s
✅ YAML	prettier	11	0	0	0	0.73s
✅ YAML	v8r	11		0	0	11.83s
✅ YAML	yamllint	11		0	0	0.7s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@9.6.0 --custom-flavor-setup --custom-flavor-linters PYTHON_BLACK,PYTHON_ISORT,COPYPASTE_JSCPD,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_BETTERLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository

[FlorianPfaff]

Superseded by #4293. This diagnostic PR intentionally forced the backend suite step to exit successfully so its failure logs could be uploaded; those artifacts exposed the eight remaining PyTorch failures. The implementation and regression fixes are now consolidated in #4293, so this temporary workflow should not be merged.