[FEATURE] Expand Next.js Interface Console Navigation Endpoints Map

Problem

Our Next.js 14 control panel console is currently limited across /dashboard and /workers folder configurations layouts. Clicking alternative tracking sidebar navigation triggers like /settings, /credentials, or /telemetry instantly flashes a broken 404 page error, dropping dashboard visualization tracking completeness metrics.

Proposed Solution

Scaffold and mount the remaining App Router page segments layout components tree under dashboard/ui/app/ coordinates:

1. /app/telemetry/page.tsx: To consume real-time asynchronous kernel stream logs via EbpfMonitor or ProxyStream widgets.
2. /app/settings/page.tsx: To handle dynamic circuit breaker properties, global routing metrics parameters, and color palettes options.
3. /app/credentials/page.tsx: To manage ingress authentication keys.

Alternatives

Running monolithic dashboard components structures on a single master file branch layout, which scales poorly and mixes visual concerns.

Use Case

Enables high-fidelity interface transparency for platform operators during Demo Day sequences, allowing real-world users to observe multi-region connection migrations smoothly with zero UI friction.

Additional Notes

Utilize our pre-configured corporate color classes (bg-red-500, bg-blue-600, bg-emerald-500, bg-amber-400) to match our Google/Microsoft high-contrast branding spectrum parameters.

Start by inspecting the existing /dashboard and /workers folder configurations and layouts under dashboard/ui/app/. Add the telemetry, settings, and credentials page segments described in the issue, then verify that the corresponding sidebar navigation paths no longer show 404 pages and expose the requested operator controls.