Pulsed module simulation proof of concept

[bradleybauer]

In some setups the local repair module(s) is not ran continuously, for example during jspace dreadnought ratting. It is more accurate to say the module is "pulsed" in this context. Because of the high capacitor usage of capital local repair modules this difference between running continuously and pulsing makes a significant difference in capacitor stability. Typically the repair module is ran only often enough to compensate for the incoming damage.

Copilot generated a proof of concept (slop code admittedly). It decided to add the "Pulse" column to the main fit page which shows the pulse interval. In the following screenshot you can see the capital shield booster is set to pulse at 10 second intervals producing a 4094.5 EHP/s recharge rate which is half of the normal recharge rate 8189 EHP/s (this shield booster has a 5s cycle time).

Clicking the pulse column at a particular row opens the "Set Pulse Interval" window for the module on that row if that module has a cycle time.

I think it would be better to not put it on the front page in front of everyone. People unfamiliar with the feature may be surprised by the popup if they accidentally click the column. Maybe it is more appropriate to add as a custom graph page? Or as a per-module custom stat that can be set by a right click menu?

I also asked copilot to fix some issues with "factor in reload time" and ancil remote reps.

Thoughts?