Make older storage format migration of third-party and bundled macros more robust when using Scroll Translations

If content pages have been created by older Confluence versions, or if pages have been created by a page template created by an old Confluence version, macros that link to pages using just the page name will be migrated – on 5.8 & 5.9 – when user edits a page to use a ResourceIdentifier instead. This migration is also triggered when macro is rendered to XHTML, which is needed for the Scroll Translations plugin. Unfortunately, the migration is broken when called in this context.

To improve the situation we should try to avoid the surplus migration when rendering to the view.