Per-Condition profiling for debug report

[vibhor1102]

The aim is to let a user seeing debug report know how much processing time each condition has eaten up. This is valuable information for them to know which conditions need to be optimized to speed up detection.

This feature requires new data to be captured by the debug report at a very low level. I'm currently working on building the foundations for it, testing prototypes. Later on, this feature can be merged into #958 development to integrate into the UI.

WIP Branch: https://github.com/vibhor1102/Smart-AutoClicker/tree/wip/condition-detection-profiling