Add IfConfigDeclSyntax support for conditional compilation

[bfahey]

📝 Summary

Protocols with #if/#elseif/#else/#endif blocks now have their members correctly mocked with the conditional compilation structure preserved. This includes support for methods, properties, initializers, and associated types within conditional blocks.

🛠️ 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?

Ran all unit tests.

🔗 Related PRs or Issues

Closes #136

✅ 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 96.87500% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 73.35%. Comparing base (ef30af4) to head (835b842).

Files with missing lines	Patch %	Lines
...MockingMacros/Macros/MockedMacro/MockedMacro.swift	96.87%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #137      +/-   ##
==========================================
+ Coverage   69.76%   73.35%   +3.59%     
==========================================
  Files          73       73              
  Lines        3678     3866     +188     
==========================================
+ Hits         2566     2836     +270     
+ Misses       1112     1030      -82     

☔ View full report in Codecov by Sentry.
📢 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]

Some comments/suggestions from my first pass through this

[berbs-fetch]

Suggested change

	var seenNames: Set<String> = []
	let uniqueAssociatedTypes = associatedTypeDeclarations.filter { decl in
	var seenNames = Set<String>()
	let uniqueAssociatedTypes = associatedTypeDeclarations.filter {
	seenNames.insert($0.name.text).inserted
	}

Q: Does order matter? If not then Set(associatedTypeDeclarations) will work

[graycampbell]

There's a hole in how all of this is implemented at the moment. See my comment below about the mock's generic parameter constraints.

[graycampbell]

There's actually an issue with this PR as it stands right now. Right here (the code contained in this if block), is why the above deduplication of the associated types by name doesn't work.

Problem

If you have a protocol like this:

protocol SomeCollection {
  #if DEBUG
  associatedtype Item: Equatable
  #else
  associatedtype Item: Hashable
  #endif
}

This current implementation is going to create this mock:

final class SomeCollectionMock<Item: Equatable>: SomeCollection {}

But that means the mock will only compile properly for DEBUG.

Possible Solution

If there are any associated types inside #if statements, we need to change how we handle the mock’s generic parameter constraints. So for the example above:

protocol SomeCollection {
  #if DEBUG
  associatedtype Item: Equatable
  #else
  associatedtype Item: Hashable
  #endif
}

We shouldn't emit:

final class SomeCollectionMock<Item: Equatable>: SomeCollection {}

We should emit:

final class SomeCollectionMock<Item> {}

#if DEBUG
  extension SomeCollectionMock: SomeCollection where Item: Equatable {}
#else
  extension SomeCollectionMock: SomeCollection where Item: Hashable {}
#endif