Detect circular dependencies [Requires: Cross-file checking]

Acceptance Criteria

• Explore how we could identify problematic circular dependencies
• Depending on the result of the exploration open a PR or present your findings to the team

Notes

• It's possible to get into an infinite loop with blocks and we wouldn't currently catch this before somebody blows up their theme
• It's also possible to have a block render a block and it not be a problem (e.g. early return if a value is set) and we wouldn't want to throw a theme check error in that case

Detect and warn on circular dependencies. Ex: Group block has a static Text block and the Text block itself has a static Group block. This can lead to infinite loop in adding a Group block preset since static blocks are added with their container (block that contains them)

Start by exploring the cross-file checking and static block/container preset handling described in the issue. Investigate how circular dependencies can cause infinite loops while allowing safe cases with early returns. Done means either opening a PR with detection and warnings or presenting the exploration findings to the team.