Add instrumentation to all *Module update methods

[JonnyOThan]

Possibly on a config toggle, but this would be a good first step in increasing the depth of profiling data. Relevant types:

• PartModule
• InternalModule
• ScenarioModule
• VesselModule
• KSPAddon

[gotmachine]

Also related to #4, note that the MethodProfiler branch has a barebones but somewhat functional prototype for this.

I more or less abandoned work on this after I started using DotTrace.

If I remember right, my initial idea was to have the ability from the UI to select specific assemblies to profile, and have automatically all the common MonoBehaviour methods (such as Update and FixedUpdate...) being profiled, as well as the KSP specific methods (OnUpdate, OnFixedUpdate...), and all coroutines.

On top of that, I was planning the ability to create, save and load custom profiling configurations ("groups") where the user could pick any amount of methods to profile from an UI listing all assemblies, types and methods available.

TBH, I don't think this whole tool is that useful for plugin devs, or at least i don't think it's really worth the effort given that there are much better off-the shelf, far more advanced solutions.

But from a player perspective, it could be interesting to have access to an easy to use tool that can show broad CPU usage metrics on a per-assembly basis (more or less the first part), as it could help them identify which mods are to blame in heavily modded installs.