feat: stack upgrades

[lwin-kyaw]

Motivation and Context

This PR upgrades the core torus-embed stack to the latest Web3Auth/Torus ecosystem versions and updates the demo app so it continues to build and run correctly after those upgrades.

The demo changes are primarily focused on keeping the example app aligned with the new controller exports and the Tailwind CSS v4 / Vite 8 setup used by the latest @toruslabs/vue-components.

Description

• upgrade the main package runtime/build dependencies, including @web3auth/ws-embed, @toruslabs/torus-scripts, TypeScript, ESLint, Prettier, webpack, and related tooling
• update the Torus wrapper to match the newer embed SDK expectations by preserving default web3AuthClientId / network setup and defaulting loginMode to "embed"
• upgrade the demo app dependencies to the latest @toruslabs/*, Vue, and Vite versions
• migrate the demo app styling to Tailwind CSS v4’s CSS-first setup using @tailwindcss/vite
• remove the legacy PostCSS config that depended on autoprefixer
• update demo dashboard initialization and supported network usage to match the newer controller API (DEFAULT_SUPPORTED_NETWORKS) and explicitly pass supported chains during init

How has this been tested?

• npm run build
• npm --prefix examples/demo-app run build

Screenshots (if appropriate):

N/A

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (dependency/runtime upgrades may affect existing behavior)

Checklist:

• My code follows the code style of this project. (run lint)
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My code requires a db migration.

---

Note

Medium Risk
Moderate risk due to broad dependency/tooling upgrades (Web3Auth/Torus SDK, build tooling, Vite/Tailwind) that can change runtime behavior and bundling output. Small wrapper API/default changes may affect integrators relying on previous init/login defaults.

Overview
Upgrades the core @toruslabs/torus-embed stack to the latest @web3auth/ws-embed and modernizes the build/lint toolchain (TypeScript/ESLint/Prettier/torus-scripts) with updated Node/npm engine requirements.

Adjusts the Torus wrapper (src/embed.ts) to align with newer embed SDK expectations by baking in default web3AuthClientId/network values and defaulting loginMode to "embed" during init.

Refreshes the demo app to match the new controller/component APIs and build setup: updates dependencies to latest @toruslabs/*, moves styling to Tailwind v4 via @tailwindcss/vite, and updates dashboard initialization to use DEFAULT_SUPPORTED_NETWORKS and pass explicit chains/chainId during torus.init().

^{Reviewed by Cursor Bugbot for commit 57aac07. Bugbot is set up for automated code reviews on this repo. Configure here.}