Add circular dependency reporting to Metamaskbot comment

[desi]

What is this about?

Store a JSON snapshot of our circular deps and monitor changes through automated checks - similar to how we handle attributions.

• Store snapshot in /madge-circular-deps.json, (we are codeowners)
• Use 'yarn circular-deps:update' to generate
• Use 'yarn circular-deps:check' to validate
• Integrate with existing GitHub workflows (metamaskbot, etc)

This gives us visibility into any circular dependency changes before they hit our codebase. We'll be able to:

• Track changes in real-time
• See exactly what code changes triggered new circular deps
• Keep a clear history of how these dependencies evolve

It's a simple start, but it'll help us make more informed decisions about our dependency structure.

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

• We can track changes over time and see where problems started.

Stakeholder review needed before the work gets merged

• Engineering (needed in most cases)
• Design
• Product
• QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• Security
• Legal
• Marketing
• Management (please specify)
• Other (please specify)

References

No response