🌶️ Hot Fix: Issue with TOS and Policies page

[frimpongopoku]

What was wrong?

When the footer menu items are sent from the backend, they are sent with no leading slashes. They are sent like this:

        {
            "id": 9,
            "name": "PortalFooterQuickLinks",
            "content": {
                "links": [
                    {
                        "link": "policies?name=Privacy%20Policy",
                        "name": "Privacy Policy",
                        "navItemId": "footer-privacy-policy-id"
                    },
                    {
                        "link": "policies?name=Terms%20of%20Service",
                        "name": "Terms of Service",
                        "navItemId": "footer-terms-of-service-id"
                    },
                    {
                        "link": "https://docs.google.com/forms/d/e/1FAIpQLScxNPrJNsyy6k834hsPdy_Rf0jaDcczRAkjCM3Z1xgYn49Zsw/viewform",
                        "name": "Report a bug/Suggest a feature",
                        "navItemId": "footer-report-a-bug-id"
                    }
                ],
                "title": "Quick Links"
            },
            "is_deleted": false,
            "is_published": false
        },

When there is no leading slash, the link is appended to whatever is in the address bar; and when that happens while a user is using the site via a custom domain, the link that will be formed will not match anything defined in our AppRouter.js.

Case in point : https://www.energynavigators.org/testimonials/policies?name=Privacy%20Policy

• [X] This PR fixes the issue. Right now, I have appended a leading slash to footer links when in custom-domain mode.

Requirements

• [x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• [x] I've tested my changes manually.
• [ ] I've added unit tests to my PR.

Transparency (Project board)

• [x] I've given my PR a meaningful title.
• [ ] I linked this PR to the relevant issue.
• [ ] I moved the linked issue from the "Sprint backlog" to "In progress" when I started this.
• [ ] I moved the linked issue to "QA Verification" now that it is ready to merge.

What kind of change does this PR introduce? (check at least one)

• [x] Bugfix
• [ ] Feature
• [ ] Performance improvement
• [ ] Feature removal
• [ ] Code style update
• [ ] Refactor
• [ ] Docs
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [ ] Yes
• [x] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• [ ] It's submitted to the dev branch or to a feature branch, not the main branch
• [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• [ ] All tests are passing:
• [ ] New/updated tests are included

Other information: Any otherthing we need to know