WS-1943-Create route in Simorgh to render Topic pages in Next.js app

[Nabeel1276]

Resolves JIRA: https://bbc.atlassian.net/browse/WS-1943

Summary

Created new route in Simorgh to render topic pages in NextJS app

Code changes

• Added new route to the Next.js app to support Topic pages, reusing existing data fetching logic from express.
• The constructPageFetchUrl function was updated so local Topic pages fetch data from the Next.js API.
• Updated local topic page URL to reflect a correct asset route structure for topics, using the correct topic ID.

Developer Checklist

• UX
  • UX Criteria met (visual UX & screenreader UX)
• Accessibility
  • Accessibility Acceptance Criteria met
  • Accessibility swarm completed
  • Component Health updated
  • P1 accessibility bugs resolved
  • P2/P3 accessibility bugs planned (if not resolved)
• Security
  • Security issues addressed
  • Threat Model updated
• Documentation
  • Docs updated (runbook, READMEs)
• Testing
  • Feature tested on relevant environments
• Comms
  • Relevant parties notified of changes

Testing

• Manual Testing required?
  • Local (Ready-For-Test, Local)
  • Test (Ready-For-Test, Test)
  • Preview (Ready-For-Test, Preview)
  • Live (Ready-For-Test, Live)
• Manual Testing complete?
  • Local
  • Test
  • Preview
  • Live

Additional Testing Steps

1. List the steps required to test this PR.

Useful Links

• Coding Standards
• Repository use guidelines
• Add Links to useful resources related to this PR if applicable.

[amoore108]

I would maybe retain similar behaviour to the current implementation here:

simorgh/src/app/routes/topic/getInitialData/index.js

Lines 11 to 21 in 1e35675

	const overrideRendererEnv = pathname => {
	if (isTest()) {
	const url = Url(pathname, true);
	if (!url.query.renderer_env) {
	url.query.renderer_env = 'live';
	}
	return url.toString();
	}
	return pathname;
	};

Not necessarily exactly this, but something like:

- if isTest AND no renderer_env then renderer_env = 'live'
- else
- use rendererEnv from context.query

[amoore108]

This is unique to topics, so just want to make sure we don't break e2es or anything by omitting this behaviour as it stands.

[amoore108]

Bit of pain but may also be worth updating these localhost:7080 references to localhost:7081 for topics routes.

[Nabeel1276]

Sorry just wanting clarity, would 7080 not work? Or is it because once we've fully migrated to NextJS the port will be 7081?

[amoore108]

7081 will be the new port number for Topics pages after this change. Technically it'll still work on 7080 until we remove the old Express app code, but I think we should direct people to the new port now.

[amoore108]

Could we add a test for this file as well? Similar pattern to the handleHomepageRoute and handleArticlePageRoute