New Rule

This rule is opt-in only while running in beta

to opt-in, use modify your .flow-scanner.yml configuration with the ff:

rules:
  RecursiveAfterUpdate:
    severity: error

Rule (Configuration ID)	Description
Recursive After Update (`RecursiveAfterUpdate`)	After updates are meant to be used for record modifications that are not the same record that triggered the flow. Using after updates on the same record can lead to recursion and unexpected behavior. Consider using before save flows for same record updates.

What's Changed

feat: add new rule on beta recursive after update opt in only by @junners in #153

Full Changelog: v3.3.0...v3.4.0