fix(SW-236): properly handle expired token in webviews

Trying out a new pattern for errors in data fetching.

Next.js is not a fan of throwing errors. Instead it recommends returning
different shapes for each state. Ref:
https://nextjs.org/docs/app/building-your-application/routing/error-handling#handling-expected-errors-from-server-components

It requires some more detailing and a bit more refactoring in non webview part,
but it is a start. This webview specific implementation should not break web.

components/Loyalty/Sidebar/MyPagesNavigation/index.tsx

@@ -1,16 +0,0 @@
-import { serverClient } from "@/lib/trpc/server"
-
-import MyPagesSidebar from "@/components/MyPages/Sidebar"
-
-import { LangParams } from "@/types/params"
-
-export default async function MyPagesNavigation({ lang }: LangParams) {
-  const user = await serverClient().user.name()
-
-  // Check if we have user, that means we are logged in.
-  if (!user) {
-    return null
-  }
-
-  return <MyPagesSidebar lang={lang} />
-}