Default to AFTER ordering instead of NONE

[FiniteReality]

Related to neoforged/MDK#118

In most cases, a mod's dependencies DO actually need to be loaded before the mod in question is loaded - the current default of NONE means that our parallel construction can initialize a mod before its dependencies, leading to potential crashes due to thread timing nonsense. We should default to AFTER so that the typical use case is more likely to be correct, even if it does mean startup time is impacted slightly due to the strict ordering.

[Technici4n]

I am against this change. Generally, there is no reason to reach for content of another mod within the same initialization phase.

[shartte]

In most cases, a mod's dependencies DO actually need to be loaded before the mod in question is loaded

Can you please back that up with some data? A ton of mods depend on JEI/EMI/REI/WTHIT/Jade where that is not correct.

[TelepathicGrunt]

Do you have examples of said crashes? I rather we simply teach people of the ordering and they can use it when it actually matters.