[Bug] Protocol that inherits from protocols in two different modules with same function name does not produce unique handlers

Environment

macOS 13.4.1
Swift version 5.8.1
Xcode 14.3.1
v2.0.1

Issue

The following code produces a mock that does not compile successfully

Protocols to Mock

// ModuleA

/// @CreateMock
public protocol Foo {
    func foo(num: Int)
}

// ModuleB

/// @CreateMock
public protocol Bar {
    func foo(text: String)
}

// Module C
import ModuleA
import ModuleB

/// @CreateMock
public protocol FooBar: Foo, Bar {}

Generated Mock

public class FooBarMock: FooBar {
    public init() { }

    public var fooCallCount = 0
    public var fooHandler: ((Int) -> ())?
    public func foo(num: Int)  {
        mockFunc(&fooCallCount)("foo", fooHandler?(num), .void)
    }
    public func foo(text: String)  {
        mockFunc(&fooCallCount)("foo", fooHandler?(text), .void) // error found here because fooHandler expects an Int, not a string
    }
}

Error

error: cannot convert value of type 'String' to expected argument type 'Int'
        mockFunc(&fooCallCount)("foo", fooHandler?(text), .void)

Start by reproducing the issue with the three Swift modules and the FooBar protocol shown in the report, then trace the mock-generation path that derives handler and call-count names. The fix is done when inherited methods with the same base name receive distinct handlers and the generated FooBarMock compiles for both Int and String arguments.