Bug/page links landing page

[A-Ashiq]

Description

• Implements a new function getPath() to be used to get the relative path associated with a given URL
• Calls this function throughout the landing page/menu so that all page links are provided to next.js as relative paths

Fixes #CDD-2224

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Unit tests
• Playwright e2e tests
• Mobile responsiveness
• Accessibility (i.e. Lighthouse audit)
• Disabled JavaScript

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• Any styles in this change follow the 'STYLES.md' guide
• My changes are progressively enhanced with graceful degredagation for older browsers and non-JavaScript users
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[sonarcloud]

Quality Gate failed

Failed conditions
61.5% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[github-actions]

Unit tests coverage

Lines	Statements	Branches	Functions
	92.38% (1759/1904)	82.35% (406/493)	89.93% (259/288)

Tests	Skipped	Failures	Errors	Time
470	0 💤	0 ❌	0 🔥	16.065s ⏱️