Cyclomatic complexity

[RubenHalman]

Rule Id	Description	Reference
Cyclomatic Complexity	The number of loops and decision rules, plus the number of decisions. Use subflows to reduce the cyclomatic complexity within a single flow, ensuring maintainability and simplicity.	tbd

This PR includes a new rule and some minor adjustments to the Flow Model, allowing for some simple metadata type preprocessing(Counting loops etc)

Todo

• Fix Flow Tests? @junners I love how ESLint now prevents a push when tests are failing, but as a result, I commented out the one failing test that I have not been able to fix yet. See also a detailed comment in the PR.
• Update docs

[junners]

Eeeey as always this is good! My stuff is a WIP, this actually follows the McCabe counting system.

Mine was more like the number of paths you can take towards the end 😂

[RubenHalman]

@junners One reason I have not proceeded with this rule is that I am unsure on what the default threshold should be. From my experience a lot of organizations are currently dealing with high cyclomatic complexity in Flows and I think we should start with a rather leniant threshold. Although it is fully configurable, I am very keen to learn what your opinion is on what could be an acceptable threshold

[junners]

My rollout plan was to atleast make it a note level, then via sfdx/vsce collect usage stats. We won't fully know until we actually get some data

[junners]

Just logged in to my personal machine. I'm looking at this rn

[junners]

Kk i've fixed some of the changes 👍🏻 I'll add in some unit tests on cyclomatic complexity

[junners]

@RubenHalman - do you think it's best to activate this upfront? Like add it in the defaultstore

Edit: Let's release this as note

[junners]

I'll do a release in the next couple of days~