Enable Consensus routing

[buberdds]

Consensus mockups don't match most of our ParaTimes views so we prob need to setup separated views. To discuss how we want to handle routes

here we can keep dynamic segments for ParaTimes and we will be able to add specific Consensus (static segment) routes

          {
            path: 'consensus',
            errorElement: withDefaultTheme(<RoutingErrorPage />),
            loader: scopeLoader,
            children: [
              {
                path: '',
                element: <ConsensusDashboardPage />,
              },
            ],
          },
          // our current runtimes paths

Will match backend design (consensus - runtimes separation) more. We keep current Paratimes as is. W can rename some stuff like :layer to :runtime if we go with splats.

possible routing options:

• dynamic segments for ParaTimes static for Consensus
• dynamic segments only
• static segments
• (breaking change) re-define routes hierarchy (mainnet/runtime/:layer, mainnet/consensus)

[github-actions]

Deployed to Cloudflare Pages

Latest commit:	855784529a64d320997f82ab895d65aab1c2e006
Status:	✅ Deploy successful!
Preview URL:	https://48141217.oasis-explorer.pages.dev

[lukaw3d]

I don't think these fields can be undefined. It would be caught by loaders. I think useScopeParam only needs to check that one of the useRouteLoaderData is found

[lukaw3d]

But that was also true previously, so was .valid not needed, and always true?

[lukaw3d]

or do we never use the errors thrown in loaders

[lukaw3d]

large refactor in #1159

[buberdds]

Refactor looks cool, thanks! let's go with #1159 in this case and just sync changelog number there.

[buberdds]

ah I can see the plan is to merge this one first.