Fix autoclosure forwarding in generated mock bodies

[graycampbell]

📝 Summary

When a mocked protocol method has an @autoclosure parameter, the generated mock body previously passed the closure directly to recordInput and the invoke closure. This caused a compile error: "Add () to forward @autoclosure parameter". The fix evaluates the autoclosure into a local let binding before use, wrapping the call in try and/or await as required by the closure's effect specifiers.

Also renames isInoutParameter → isInout and isConsumingParameter → isConsuming in MockedMethodMacro+BodyMacro.swift to better follow Swift API Design Guidelines (omit needless words — the Parameter suffix was redundant given the argument label).

compilationCondition: .none is added to every @Mocked usage in MockingClient. Without it, the default .swiftMockingEnabled condition wraps each generated mock in #if SWIFT_MOCKING_ENABLED, so the mock bodies are never compiled during a regular swift build — defeating the purpose of the client as a compilation verification target.

🛠️ Type of Change

• Bug fix (change that fixes an issue)
• New feature (change that adds functionality)
• Breaking change (bug fix or feature that is not backwards compatible)
• Documentation (DocC, API docs, markdown files, templates, etc.)
• Testing (new tests, updated tests, etc.)
• Refactoring or code formatting (no logic changes)
• Updating dependencies (Swift packages, Homebrew, etc.)
• CI/CD (change to automated workflows)
• Chore (other maintenance)

🧪 How Has This Been Tested?

Eight macro expansion tests in MockedMethod_AutoClosureTests, covering all four effect-specifier variants × two autoclosure return type variants (void and non-void):

Test	Autoclosure type	Method effects
autoClosureWithVoidReturnType	() -> Void	—
autoClosureWithNonVoidReturnType	() -> Int	—
asyncAutoClosureWithVoidReturnType	() async -> Void	async
asyncAutoClosureWithNonVoidReturnType	() async -> Int	async
throwingAutoClosureWithVoidReturnType	() throws -> Void	throws
throwingAutoClosureWithNonVoidReturnType	() throws -> Int	throws
asyncThrowingAutoClosureWithVoidReturnType	() async throws -> Void	async throws
asyncThrowingAutoClosureWithNonVoidReturnType	() async throws -> Int	async throws

Each test verifies the correct let autoClosure = [try] [await] autoClosure() binding is generated, the appropriate effect specifiers appear on the invoke call, and the peer type (MockVoidParameterized[Async][Throwing]Method) and closure type are correct.

AutoClosures.swift in MockingClient is updated with all eight corresponding methods, serving as an end-to-end compilation check.

🔗 Related PRs or Issues

Fixes #134

✅ Checklist

• I have added relevant tests
• I have verified all tests pass
• I have formatted my code using SwiftFormat
• I have updated documentation (if needed)
• I have added the appropriate label to my PR
• I have read the contributing guidelines
• I agree to follow this project's Code of Conduct

[codecov]

Codecov Report

❌ Patch coverage is 93.24324% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.12%. Comparing base (6e676a2) to head (fb057ea).

Files with missing lines	Patch %	Lines
...ockedMethodMacro/MockedMethodMacro+BodyMacro.swift	92.30%	4 Missing ⚠️
...kedMethodMacro/MockedMethodMacro+TypeErasure.swift	95.23%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #146      +/-   ##
==========================================
+ Coverage   78.42%   80.12%   +1.69%     
==========================================
  Files          73       73              
  Lines        4055     4120      +65     
==========================================
+ Hits         3180     3301     +121     
+ Misses        875      819      -56     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

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

[graycampbell]

compilationCondition: .none needs to be added to every @Mocked usage in MockingClient. Without it, the default .swiftMockingEnabled condition wraps each generated mock in #if SWIFT_MOCKING_ENABLED, so the mock bodies are never compiled during a regular swift build, defeating the purpose of the client as compilation verification.