Better/easier support for multi-site/domain link resolution in RTE Delivery API

[MiguelGuedelha]

Applicable versions

• v13
• v16
• v17

Use case

• 2 root nodes are setup in a CMS
• These roots have full content trees under them
• Each node has distinct domains setup for them
• Somewhere in the content tree, a node (call it X) with a RTE field has an embedded link, with the picker set to a content node (call it Y) which exists in the other site where node X is not in.
• Currently both the JSON and HTML output modes put out a bunch of data such as Start Item path, Start Item ID, a "resolved" path, etc. However, unlike regular links in say a MultiNodeTreePicker (MultUrlPicker in more recent versions), the actual Destination ID guid of the target node is completely missing (in the rich text parser base I think it is there, but seems to be cleaned out)
  • This destination ID remaining present makes it very easy to resolve absolute path/domain/url data for a given node and simplifies absolute vs relative URL building logic on said BFF or even frontend layers (usually through some solution specific URL resolution service)

The main suggestion here is to preserve the target node's Content GUID and type in the link's info (both JSON and Markup formats)

Will provide a solution PR for v17, porting down over to 16/13 should in theory be simple enough if basing off the main dev branch of each version as the change will be the same and not affect the main 13 -> 17 changes in the affected files (caches, etc)