Dealing with variant URLs is a complicated issue. The rules for variants are different depending on which API or content you are dealing with. Many clients have implemented logic to deal with this, and this code basically has to be rewritten on every client, usually with a different set of bugs.
Most of this could be solved by returning all the URLs needed by clients so they never have to figure out how to mangle the titles.
This ticket has two major components:
1. Return an exhaustive dictionary of URLs and titles for all variants of the page
2. Ensure the primary titles and URLs in the summary response are actually correct and take into account the idiosyncrasies of manipulating variant URLs for each API
The structure will be something like the top level dictionaries, but scoped to each variant:
Some pen questions:
1. The implementing engineers will need to research this a bit further to see if this is a good structure
2. Do we need other information like marking the "canonical" variant?