Downgrade sublibrary CI has resolver conflicts

[ChrisRackauckas-Claude]

Current PR CI on DataDrivenDiffEq shows downgrade-sublibrary resolver failures that appear unrelated to the changed code and affect multiple sublibraries. Recent master CI also shows downgrade-sublibrary failures.

Examples from PR #631 CI:

downgrade-sublibraries / test (lib/DataDrivenSparse)
ERROR: LoadError: Unsatisfiable requirements detected for package BracketingNonlinearSolve [70df07ce]

downgrade-sublibraries / test (lib/DataDrivenSR)
ERROR: LoadError: Unsatisfiable requirements detected for package SymbolicRegression [8254be44]:
  restricted to versions 1 by DataDrivenSR
  restricted to versions 1.0.0 by an explicit requirement
  restricted by compatibility requirements with SymbolicUtils [d1185830] to versions [0.1.0-0.2.0, 1.13.0-1.13.2] or uninstalled — no versions left
  SymbolicUtils is restricted to versions 4 by DataDrivenDiffEq

downgrade-sublibraries / test (lib/DataDrivenLux)
ERROR: LoadError: Unsatisfiable requirements detected for package DataInterpolations [82cc6244]

These are resolver failures before package tests run. The failing workflow uses Julia 1.10 and allow_reresolve=false in the sublibrary downgrade matrix.

This was noticed while checking unrelated PR #631; the changed sublibrary's normal Core and QA jobs passed, but the downgrade-sublibraries resolver jobs failed.

[ChrisRackauckas-Claude]

Draft fix PR opened: #634. It raises the stale lower bounds exercised by the sublibrary downgrade workflow. Locally reproduced and passed the DataDrivenSparse, DataDrivenSR, and DataDrivenLux downgrade test paths with allow_reresolve=false.