[Feature]: Decouple the landing pages between the portal implementations

[Tzal3x]

Description

The server portal's landing page is being fetched by the service worker portal. i.e. both serve the same landing page. This means that a redundant service worker is also installed to the user's browser.

A new landing page imlementation should be included to the server portal. Ideally, taking advantage of the web framework used. e.g.

• hono can serve jsx/tsx and static files but has an issue with custom fonts and images.
• nextjs can also serve tsx but raw static file serving is also problematic.

The landing page could be re-implemented in tsx, simplifying the structure.

Or there can be a landing page server that is only responsible for managing the static file content.

Component

portal

Code of Conduct

• [X] I agree to follow this project's Code of Conduct.

[Tzal3x]

The landing page can also be served as a walrus site, erasing the need for a separate landing page server. Issue: https://github.com/MystenLabs/walrus-sites/issues/173 ⚠️ This could possibly be a bit slower, but we can monitor the impact of it after we merge.