World-age changes in 1.12

[Samuel-amap]

I see world-age behaviour was slightly changed in 1.12. This release occurred after the implementation of automatic input vector to model generation was added to PlantSimEngine.

I don't think anything broke on our end (tests pass without issues), but since we may need to work on automated model generation in other circumstances (multi-timestep, etc.), it is worth looking into the exact nature of the changes and potential consequences and subtleties.

A section about world-age was added in the manual : https://docs.julialang.org/en/v1.12.0-rc2/manual/worldage/

[Samuel-amap]

Addendum :

I believe it should be possible for us to generate models on the fly, and call invokelatest when we need to call the run! function of those models, to raise the world-age temporarily and ensure those functions are visible and callable without needing to force a clunky return to toplevel first.

Situations where generating models and executing on-the-fly code currently only involve status vector inputs, and timestep mapping, but world-age clunkiness was a blocker.

There may still be concerns (performance ?), but the invokelatest approach may be worth testing, and is considered to be stable.

[VEZY]

Fixed in #184