Error precompiling `SymbolicsPreallocationToolsExt`

[IanButterworth]

This may have overlap with other open extensions issues, but here's a tracking issue to debug it.

A couple of things of note:

• SymbolicsPreallocationToolsExt doesn't actually fail its precompile job, just @error's
• It looks like SymbolicsPreallocationToolsExt is being loaded in the precompile worker via a trigger before it specifically tries to precompile SymbolicsPreallocationToolsExt and I assume succeeds because the worker doesn't fail

(@v1.11) pkg> st
Status `~/.julia/environments/v1.11/Project.toml`
  [d236fae5] PreallocationTools v0.4.17
  [295af30f] Revise v3.5.13
  [0c5d862f] Symbolics v5.17.0 `~/.julia/dev/Symbolics`

(@v1.11) pkg> precompile
Precompiling project...
  21 dependencies successfully precompiled in 25 seconds. 122 already precompiled.
  1 dependency had output during precompilation:
┌ Symbolics → SymbolicsPreallocationToolsExt
│  ┌ Warning: Module SymbolicsPreallocationToolsExt with build ID ffffffff-ffff-ffff-0008-4f3de8c9c66b is missing from the cache.
│  │ This may mean SymbolicsPreallocationToolsExt [d479e226-fb54-5ebe-a75e-a7af7f39127f] does not support precompilation but is imported by a module that does.
│  └ @ Base loading.jl:2113
│  ┌ Error: Error during loading of extension SymbolicsPreallocationToolsExt of Symbolics, use `Base.retry_load_extensions()` to retry.
│  │   exception =
│  │    1-element ExceptionStack:
│  │    Error when precompiling module, potentially caused by a __precompile__(false) declaration in the module.
│  └ @ Base loading.jl:1380
└  

cc. @ChrisRackauckas

[IanButterworth]

ForwardDiff is an indirect dep of PreallocationTools. Maybe that's related

(@v1.11) pkg> why ForwardDiff
  PreallocationTools → ForwardDiff
  Symbolics → SymbolicUtils → LabelledArrays → ForwardDiff

Symbolics exts:

[extensions]
SymbolicsGroebnerExt = "Groebner"
SymbolicsPreallocationToolsExt = ["ForwardDiff", "PreallocationTools"]
SymbolicsForwardDiffExt = "ForwardDiff"
SymbolicsSymPyExt = "SymPy"

[RaimundK]

The issue is still present.

[KristofferC]

Fixed by #53972