Remove Suspense wrappers from public policy routes

[SaravanakumarR2018]

Motivation

• The public policy pages were wrapped in Suspense with a LoadingPage fallback but do not require lazy-loading behavior.
• Simplify routing to render static policy pages directly and avoid unnecessary loading fallbacks.

Description

• Removed Suspense wrappers for TermsOfServicePage, PrivacyPolicyPage, and RefundPolicyPage in src/frontend/src/routes.tsx so they are now rendered as element={<TermsOfServicePage />} (and equivalents).
• The change updates only src/frontend/src/routes.tsx and reduces the Suspense-related boilerplate around these routes.

Testing

• No automated tests were run for this change.
• CI/build was not executed as part of this change.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cab22855b4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restore Suspense boundary for lazy policy pages

These policy routes still render React.lazy components (TermsOfServicePage, PrivacyPolicyPage, RefundPolicyPage are declared with lazy(...) at the top of this file). With the Suspense wrappers removed, navigating to these routes will throw at runtime (“a component suspended while rendering, but no fallback UI was specified”) because this branch of the route tree only has ContextWrapper/Outlet and no ancestor Suspense boundary. This means public policy pages will fail to render in production unless a higher-level Suspense is reintroduced.

Useful? React with 👍 / 👎.