Recognize SCPH5552 outputs and retain its SDK inputs

[Alexbeav]

SCPH5552 titles can finish generation and then stop because both build-readiness checks recognize only OpenBIOS and SCPH1001 output. The shared SDK harvest also drops the SCPH5552 profile and seed file. This change recognizes the existing backend and retains those two source inputs, while keeping the owned BIOS image out of the shared SDK.

Validation against unchanged upstream 99e0238f53356b63d966d9dfe6f0abaacc578d17:

• Production-function fixture: 15 synthetic assertions pass after the correction. Four fail on the baseline. Existing OpenBIOS/SCPH1001 controls still pass; missing files, wrong suffixes, directory lookalikes and missing game output still fail readiness.
• Two additional checks on a completed owned-input GITS setup fail before and pass after (17 total after, 6 failures before).
• The full corrected Windows CLI builds, harvests its SDK, generates SCPH5552 and game output, compiles, installs and launches GITS from the exact setup kit. The installed game exits normally after window close, at frame 2232. This used a local source override and an existing portable toolchain; public download, hub UI, audio, visual and gameplay checks are outside this result.

Run the synthetic check with python scripts/test_psx_bios_readiness.py --cxx g++. Add --baseline-ref 99e0238f53356b63d966d9dfe6f0abaacc578d17 for the failing control. The fixtures contain no retail data. The patch preserves the title's selected BIOS policy.

Developed with AI assistance; validated as described (test evidence in PR body). AI writes the code and the PR, but I always test before I send something up. Happy to iterate on this process with your feedback.

[TechnicallyComputers]

I don't know that we have 5552 support yet, and it needs handling in the generate & build and netplay lobby, and settings window for rebuild prompts, as well so I'll just leave this open for now.