Fixits produce invalid references when used with the regular markdown link syntax

[theMomax]

Description

Fixits (see #438) produce invalid references when used with the regular markdown link syntax (e.g. [doc:my/reference](doc:my/reference), or [custom title](doc:my/reference)).

The reason for that is that the code generating the replacements can only differentiate between symbol-link (``my/reference``) and non-symbol-link. It always assumes the reference to be written in DocC's custom link syntax (<doc:my/reference>) in the non-symbol-link case and thus uses wrong offsets when encountering a link written in the standard markdown link syntax ([doc:my/reference](doc:my/reference), or [custom title](doc:my/reference)).

Checklist

• If possible, I've reproduced the issue using the main branch of this package.
• This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior

Assuming that e.g. MyClass/init() requires the disambiguation suffix -33vaw for init(), the fixit should transform the link as follows:

[custom title](doc:MyClass/init()) -> [custom title](doc:MyClass/init()-33vaw)

Actual behavior

[custom title](doc:MyClass/init()) -> [custom title](doc:-33vawMyClass/init())

Steps To Reproduce

With DOCC_USE_HIERARCHY_BASED_LINK_RESOLVER=YES, run SymbolTests/testUnresolvedReferenceWarningsInDocumentationExtension() after adding the faulty link - [custom title](doc:MyClass/init()) to the initial extension comment and analyse the resulting problem as it is done for the others.

Swift-DocC Version Information

This bug was introduced in #455

Swift Compiler Version Information

swift-driver version: 1.62.15 Apple Swift version 5.7.2 (swiftlang-5.7.2.135.5 clang-1400.0.29.51)
Target: arm64-apple-macosx13.0