Remove remaining TODOs from the documentation

Author: Samuel-amap

docs/src/developers.md

@@ -122,4 +122,4 @@ Not all combinations of weather data structure/weather dataset size/status sizes
 
 They were briefly mentioned earlier in the page, but the test banks to increase the number of combinations tested for in terms of weather data, modellists/mappings and tracked outputs, could definitely be improved upon.
 
-TODO extra section on memory allocations, type stability etc.
+Some additional work and tests regarding tracking memory allocations, type stability etc. would also be worth implementing/documenting.

docs/src/prerequisites/julia_basics.md

@@ -52,8 +52,4 @@ Also of importance:
 
 Many of these are also briefly presented in [this Julia Data Science](https://juliadatascience.io/julia_basics) guide, which also happens to focus on the DataFrames.jl package.
 
-Understanding more about methods, parametric types and the typing system is usually worthwhile, when working with Julia packages.
-
-TODO point to Rémi's videos ? Other videos ?
-TODO extra concepts useful for developers ?
-
+Understanding more about methods, parametric types and the typing system is usually worthwhile, when working with Julia packages.

docs/src/troubleshooting_and_testing/implicit_contracts.md

@@ -64,12 +64,6 @@ This rule avoids potential ambiguity which could then cause both problems in ter
 
 A workaround for some of the situations where this occurs is described here : [Having a variable simultaneously as input and output of a model](@ref)
 
-## TODO Organs missing in the MTG but declared in the mapping ?
-
-## Status template intialisation order TODO 
-
-## TODO simulation order, node order, etc.
-
 ## Simulation order instability when adding models
 
 An important aspect to bear in mind is that PlantSimEngine automatically determines an order in which models are run from the dependency graph it generates by coupling models together. 

docs/src/troubleshooting_and_testing/tips_and_workarounds.md

@@ -107,8 +107,6 @@ out_pseudo_multiscale_successful = run!(mtg, mapping_pseudo_multiscale_adjusted,
 
 This feature is likely to break in simulations that make use of planned future features (such as mixing models with different timesteps), without guarantee of a fix on a short notice. Again, bear in mind it is mostly a convenient shortcut for prototyping, when doing multi-scale simulations.
 
-TODO workaround status initialisation bug ?
-
 ## Cyclic dependencies in single-scale simulations
 
 Cyclic dependencies can happen in single-scale simulations, but the PreviousTimestep feature currently isn't available. Hard dependencies are one way to deal with them, creating a multi-scale simulation with a single effective scale is also an option.