Check the module name to know when to skip inherited doc comments.

[d-ronnqvist]

Bug/issue #, if applicable: rdar://92185538

Summary

This updates Swift-DocC to use the new doc comment module information added in swiftlang/swift#58857 and swiftlang/swift-docc-symbolkit#42 to know when

Dependencies

This directly depend on swiftlang/swift-docc-symbolkit#42
The new doc comment module information is only available with swiftlang/swift#58857

Testing

With a recent trunk toolchain that include swiftlang/swift#58857

Create a project with two targets.

In the first target, define some public type and define a public protocol with links to the public type in its documentation. For example:

public protocol FirstProtocol {
   /// Documentation from the `First` target.
   ///
   /// Links to another type in the `First` target: ``FirstStruct``.
   func something()
}

public struct FirstStruct {}

In the second target, define a type that conform to the first target's protocol without overriding its documentation.

import First

public struct SecondStruct: FirstProtocol {
    public func something() {}
}

When building documentation for the second target, there shouldn't be warnings that the "Topic reference 'FirstStruct' couldn't be resolved."

Checklist

Make sure you check off the following items. If they cannot be completed, provide a reason.

• Added Updated tests
• Ran the ./bin/test script and it succeeded
• Updated documentation if necessary

[d-ronnqvist]

@swift-ci please test

[d-ronnqvist]

@swift-ci please test

[d-ronnqvist]

@swift-ci please test

[QuietMisdreavus]

Looks good!

[d-ronnqvist]

@swift-ci please test

[d-ronnqvist]

@swift-ci please test