Revisit IDDFS algo for a huge number of flows that has more than 30 elements each flow

[junners]

Currently it is only possible to select a folder and analyse all flows. In my current project we have 150+ flows and it is causing a Visual Studio timeout when I want to run them all. (Macbook Pro M1 Max)
So it would be better to choose from another screen which flow you want to analyse. Default select can be all flows but in my case it would be helpful to only analyse Case, Account or only FlowType = Screenflow.

If we break this down there's two issues -
1st is a potential performance issue on using IDDFS algo, need to have a solid case to replicate this
2nd is the ability to scan flows from a segment (Autolaunched, Screen types & etc)

This idea will be tackling the 1st point

[RubenHalman]

@junners
My suspicion is that the biggest performance improvement can be achieved if we were running all rules at the same time, whereas in the current implementation the IDDFS algorithm is applied to every rule individually to 'build the flow' although not ALL rules implement IDDFS.

Current implementation:
Rule 1, performs IDDFS...
Rule 2 performs IDDFS...
Rule 3 performs IDDFS...

A better implementation would probably execute IDDFS only once and include all rules. So it only 'builds' each flow once.