chore: update deps

[hieu-w]

Motivation and Context

Jira Link:
https://consensyssoftware.atlassian.net/browse/W3APD-5352

Description

• Remove umd build & webpack
• Upgrade all deps to latest
• Drop node 20 support. All repos .nvmrc min as node 22
• Docker files should run on node 24
• keep node 24 as active and all lock files to point to node 24
• Update sentry to v10
• Remove usage of buffer, process, bn.js

How has this been tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

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
Broad dependency/toolchain upgrades plus new Node runtime requirements (>=22 locally, Node 24 in Docker) can cause build or runtime regressions across packages. Changes are mostly infra/deps, but they affect how artifacts are built and how the server runs.

Overview
Updates the monorepo toolchain and dependencies (e.g., lerna, torus-scripts, eslint, typescript, tsx, dotenv) and regenerates the lockfile to match the new versions.

Raises runtime/build requirements by setting engines.node to >=22.x, updating .nvmrc to Node 24, and using node:24-alpine in Dockerfile.dev for local/dev builds.

Modernizes server dependencies/instrumentation by moving @toruslabs/fnd-server to @sentry/node v10 and aligning related logging/instrumentation packages.

^{Written by Cursor Bugbot for commit 3222356. This will update automatically on new commits. Configure here.}