Add public Terms, Privacy, and Refund policy pages (legacy frontend)

[SaravanakumarR2018]

Motivation

• Provide Paddle with accessible legal pages by adding Terms of Service, Privacy Policy, and Refund Policy pages to the legacy frontend.
• Confirm that the offering is fully automated with no human-driven services and document subscription billing and the no-refund stance.
• Make the pages accessible to all visitors (authenticated and unauthenticated) from stable, legacy routes without touching the new frontend.
• Keep changes minimal by adding new files and only updating the legacy landing footer and router.

Description

• Added three new pages: src/frontend/src/pages/TermsOfServicePage/index.tsx, src/frontend/src/pages/PrivacyPolicyPage/index.tsx, and src/frontend/src/pages/RefundPolicyPage/index.tsx that document service overview, billing, cancellation, and the no-refund policy.
• Exposed public routes in src/frontend/src/routes.tsx via lazy imports and new route entries at /terms-of-service, /privacy-policy, and /refund-policy so they are reachable without authentication.
• Updated the legacy landing page footer src/frontend/src/pages/LandingPage/index.tsx to link to the new policy URLs.
• Made only minimal edits to existing files and added the new pages under the legacy frontend as requested.

Testing

• Ran npm --prefix src/frontend install to install frontend dependencies which completed successfully (audit warnings present).
• Started the legacy frontend dev server with npm --prefix src/frontend run dev:docker (Vite) and verified the server was reachable.
• Automated a Playwright script to navigate to http://127.0.0.1:4173/terms-of-service and capture a screenshot, which completed successfully and produced an artifact.
• No unit/integration test suites were executed as part of this change.

---

Codex Task