User-facing performance transparency

[TeamDman]

Right now, SFM provides users the GUI graph that shows tick times.
This graph can move quite quickly if using an every-tick timer trigger.
There is also the logs gui that shows how long each statement takes to execute, though this is tedious to use when many triggers are present.

A spark profile can reveal when other mods are contributing to the time it takes SFM to do its work.
Laggoggles/Observable mod can show time taken as an in-world overlay, though the way it amortizes SFM tick time is not obvious.

Improvement goals:

• editor showing time taken per line of code in the gutter next to line numbers
• complication: if the user edits the code, the perf gutter numbers will become misaligned

sidestep the problem by producing an independent immutable report that shows the time taken for each part of the code in a text representation.

Things that take time:

• calling the insert/extract simulate/execute permutations on blocks from other mods
  • give a breakdown on the time taken by "block"
  • sfm:manager (20ms total)
  • ae2:interface (18ms)
• matching the tags on an item
• matching resource ids using the predicates
• gathering slots from blocks

[TeamDman]

for the logs, the manager should be able to capture the time taken to execute each trigger independently for the past X times for each trigger, then give the user a breakdown.

Currently, the user has to sometimes disable more frequent triggers to analyze specific ones that don't run as much