fix(deps): unblock fbuild 2.5.25 lock resolution on Python 3.13

[zackees]

Context

Updating the dependency pin from fbuild==2.5.24 to fbuild==2.5.25 caused the editor PostToolUse hook to report a non-blocking resolver failure. Reproducing the intended validation with:

uv lock --python 3.13

reported: No solution found when resolving dependencies for split (markers: ...).

The visible hook output is truncated after the marker clause, so the incompatible requirement is not yet identified.

Proposal

Reproduce the Python 3.13 lock resolution failure from a clean environment, identify the conflicting marker or package constraint introduced by fbuild==2.5.25, and either publish compatible metadata/artifacts or document and enforce the supported Python range.

Acceptance criteria

• RED -> GREEN: add a focused resolver regression test or fixture that initially reproduces uv lock --python 3.13 failing with the 2.5.25 pin.
• Identify the exact conflicting requirement and marker in a failure report.
• uv lock --python 3.13 succeeds for supported package configurations, or project metadata explicitly prevents the unsupported combination with an actionable error.
• Verify the lock on the supported CI Python versions as well as Python 3.13.

Decisions

• File this against FastLED/fbuild, the repository named by the dependency and working checkout.
• Treat the PostToolUse failure as real despite its non-blocking status: an explicit uv lock --python 3.13 must be a reliable developer validation path.

Open questions

• The full resolver conflict text was truncated in the hook output; attach it when reproduced.
• It is not yet known whether the incompatibility is fbuild metadata, a transitive dependency, or the consuming project marker set.