Add CascadeIfDirty property to make optimization opt-in

[rockfordlhotka]

Fixes #3721

[rockfordlhotka]

@lwmorris067 and @hurcane - here's the PR for my proposed fix to the breaking change around running rules.

[hurcane]

This appears to restore the original non-performant behavior by default, while still implementing the slightly optimized behavior that @mtavares628 can take advantage of.

I would still vote for the changes proposed in discussion #3720, but I understand the motivation to implement this now because it's holding back the next release.

If the other proposal were to be implemented, the CascadeIfDirty option wouldn't really be needed, would it?

[rockfordlhotka]

@hurcane I remain open to your idea, but need to see more specifics. I'm unlikely to have time to implement/test it in the next 10-14 days due to work/travel.

Update - I see your wonderfully detailed post with details, thank you!! I've captured it in #3736

[mtavares628]

This looks good to me. I do think that @hurcane's #3736 concept may be the more efficient way to go in the end (or even a combination of both of these), but just taking a look at the code that is already there it seems like it may require some re-work of CheckRulesForProperty because it doesn't currently expose the list of the rule's DirtyProperties, only the AffectedProperties.