Fix wrong SafeTestsets UUID in test extras (unbreaks master CI)

[ChrisRackauckas-Claude]

Problem

All master CI jobs (Core, QA on 1/lts, and Downgrade) are red. They all fail at test-dependency resolution, before any test code runs:

expected package `SafeTestsets [1201f925]` to be registered
 You may have provided the wrong UUID for package SafeTestsets.
 Found the following UUIDs for that name:
  - 1bc83da4-3b8d-516f-aca4-4fe02f6d838f from registry: General

The SciMLTesting v1.2 folder conversion (#163) added SafeTestsets to the test extras with an invalid UUID 1201f925-eb70-4ca8-ba2c-9b673ab8e7da, which matches no registered package. The Downgrade job hits the same error when it merges the project's SafeTestsets extra into the resolver.

Fix

Correct the UUID to the registered SafeTestsets UUID 1bc83da4-3b8d-516f-aca4-4fe02f6d838f (verified against the live General registry) in both places it appears:

• Project.toml [extras]
• test/qa/Project.toml [deps]

SciMLTesting's UUID in the same files was already correct.

Local verification (Julia 1.10, the [compat] floor)

• QA group: QA/qa.jl | Pass 10 / Total 10 — Testing PolyChaos tests passed. (Aqua's test_project_extras now passes, which would otherwise also flag the bad UUID.)
• Core group: all files green (polynomial_chaos 5175/5175, recurrence_coefficients 10510/10510, types 3427/3427, etc.) — Testing PolyChaos tests passed, exit 0.

Two-line metadata change; no Julia source touched, so Runic is not applicable.

Please ignore until reviewed by @ChrisRackauckas.