Make AttributeBodyVisitor visit mutating

[Kyle-Ye]

Summary

• Mark AttributeBodyVisitor.visit as mutating so visitor implementations can keep state while traversing attribute bodies.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 32.10%. Comparing base (c05ccf5) to head (bd7d729).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #226      +/-   ##
==========================================
+ Coverage   31.08%   32.10%   +1.02%     
==========================================
  Files          71       71              
  Lines        2635     2601      -34     
==========================================
+ Hits          819      835      +16     
+ Misses       1816     1766      -50     

Flag	Coverage Δ
ios	32.11% <ø> (+0.95%)	⬆️
macos	10.15% <ø> (+6.92%)	⬆️
ubuntu	12.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 11 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[augmentcode]

🤖 Augment PR Summary

Summary: Makes AttributeBodyVisitor.visit(body:) a mutating requirement.
Why: Enables visitor implementations to keep internal state while traversing attribute bodies via visitBody(_:).

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

Sources/OpenAttributeGraph/Attribute/Body/AttributeBodyVisitor.swift:8 — With visit now mutating, any struct/enum conformers must also mark their implementation as mutating or they will no longer satisfy AttributeBodyVisitor (e.g., the Visitor in Tests/OpenAttributeGraphCompatibilityTests/Attribute/Attribute/AnyAttributeCompatibilityTests.swift). Consider ensuring internal/downstream conformers are updated accordingly.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}