Migrate run_qa to SciMLTesting 1.5 minimal form

SciMLTesting 1.5.0 makes Aqua and ExplicitImports its own direct deps and
auto-detects them, with JET still a weakdep (opt-in via `using JET`).
`explicit_imports` stays an explicit opt-in (defaults false).

- test/qa/qa.jl: collapse to the minimal form. Imports become
  `using SciMLTesting, ADTypes, Test` + `using JET`; drop `using Aqua` and
  `using ExplicitImports`. The run_qa call drops the now-auto-detected
  `Aqua = Aqua`, `JET = JET`, `jet = true`, and `ExplicitImports = ExplicitImports`
  module args, keeping only the genuine per-repo overrides
  (aqua_kwargs, jet_kwargs, explicit_imports = true, ei_kwargs).
- test/qa/Project.toml: drop ExplicitImports from [deps]/[compat] (now
  transitive via SciMLTesting); bump SciMLTesting compat to 1.5. Aqua is kept
  as a direct dep on purpose: Aqua's ambiguity check spawns a worker
  subprocess that runs a bare `using Aqua` against the active project, which
  errors ("Package Aqua not found in current path") if Aqua is only a
  transitive (manifest-only) dep. JET is kept (the qa runs JET).
- Project.toml: bump SciMLTesting compat to 1.5.

Verified locally against the released SciMLTesting 1.5.0 (Pkg-resolved, no
dev-from-branch): QA group 17/17 on Julia 1.10 and 1.11, running the same
checks as before — all Aqua checks (incl. Method ambiguity), the six
ExplicitImports checks, and JET.test_package.

Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: ChrisRackauckas

Project.toml

@@ -18,7 +18,7 @@ ChainRulesCore = "1.0.2"
 ConstructionBase = "1.5"
 EnzymeCore = "0.5.3,0.6,0.7,0.8"
 SafeTestsets = "0.1, 1"
-SciMLTesting = "1.4"
+SciMLTesting = "1.5"
 julia = "1.10"
 
 [extras]

test/qa/Project.toml

@@ -1,7 +1,6 @@
 [deps]
 ADTypes = "47edcb42-4c32-4615-8424-f2b9edc5f35b"
 Aqua = "4c88cf16-eb10-579e-8560-4a9242c79595"
-ExplicitImports = "7d51a73a-1435-4ff3-83d9-f097790105c7"
 JET = "c3a54625-cd67-489e-a8e7-0a5a0ff4e31b"
 SafeTestsets = "1bc83da4-3b8d-516f-aca4-4fe02f6d838f"
 SciMLTesting = "09d9d899-5365-40a9-917a-5f67fddea283"
@@ -13,9 +12,8 @@ ADTypes = {path = "../.."}
 [compat]
 ADTypes = "1"
 Aqua = "0.8"
-ExplicitImports = "1.11"
 JET = "0.9, 0.10, 0.11"
 SafeTestsets = "0.1, 1"
-SciMLTesting = "1.4"
+SciMLTesting = "1.5"
 Test = "1"
 julia = "1.10"

test/qa/qa.jl

@@ -1,18 +1,15 @@
-using ADTypes
-using Aqua: Aqua
-using ExplicitImports: ExplicitImports
-using JET: JET
-using SciMLTesting: run_qa
-using Test
+using SciMLTesting, ADTypes, Test
+using JET
 
+# Aqua and ExplicitImports are SciMLTesting deps, so they are not imported here.
+# Aqua is still listed in this env's `[deps]` (not ExplicitImports): Aqua's ambiguity
+# check spawns a worker subprocess that runs a bare `using Aqua` against the active
+# project, which only resolves if Aqua is a *direct* dep — a transitive (manifest-only)
+# Aqua makes that worker error with "Package Aqua not found in current path".
 run_qa(
     ADTypes;
-    Aqua = Aqua,
     aqua_kwargs = (; deps_compat = (; check_extras = false)),
-    JET = JET,
-    jet = true,
     jet_kwargs = (; target_defined_modules = true),
-    ExplicitImports = ExplicitImports,
     explicit_imports = true,
     # Two unavoidable non-public `Base` names, ignored only in the public-API access
     # check (every other ExplicitImports check passes unignored):