fix: resolve workspace MetaMask packages from the monorepo root

[ulissesferreira]

Explanation

Status: working ✅ — verified via tsc --noEmit, tsc --traceResolution, full builds, and a real snaps-jest run.

• Changes the shared paths entry in tsconfig.packages.json to resolve @metamask/* relative to the monorepo root (./packages/*/src) instead of relying on an unset/inherited baseUrl, which is what made the previous ../*/src mapping fragile (only correct if the consumer happened to be a sibling directory).
• A local src candidate is used only when it exists on disk; otherwise resolution falls through to the installed node_modules package — so importing a published @metamask/* package not in this repo is unaffected.
• Adds @metamask/snap-networks-utils/* as an explicit subpath mapping (TypeScript paths patterns only allow one *), covering extra entry points like /logger.
• Adds tsconfig.snaps.json as a shared config for snap packages, with composite: false and no baseUrl, so they can typecheck sibling workspace source without project-reference build artifacts.
• Snap configs deliberately don't set baseUrl unless they also re-declare the paths mapping relative to it (solana-wallet-snap does this to keep baseUrl-relative src/... imports).
• Updates jest.config.packages.js's moduleNameMapper to the same local-source-then-installed-package rule.
• Logger now assigns optional prefix/decorators only when provided, so solana-wallet-snap (exactOptionalPropertyTypes) can typecheck against workspace source.
• Along the way, consolidates some per-package compiler options into the shared configs — flagged separately as it dropped a couple of options (module/moduleResolution for bitcoin-wallet-snap/sample-snap) that turned out to be silent behavior changes rather than pure dedup.

Pros and Cons

Pros:

• Single source of truth: the @metamask/* mapping lives once in the shared tsconfig.packages.json, so adding a new workspace package requires no per-package config change.
• Simplest mental model — resolution behavior is centralized and consistent for every package by default.
• Least ongoing maintenance burden as the monorepo grows (more snaps/libraries later).

Cons:

• Packages lose baseUrl-relative import ergonomics (e.g. from 'src/entities') unless they opt back in and re-declare paths anyway — which is exactly what fix: restate workspace @metamask/* paths per package with local baseUrl #169 does, partially undermining the "shared config" simplicity.
• Consolidating configs surfaced silent behavior changes (dropped module/moduleResolution overrides for bitcoin-wallet-snap/sample-snap) — a reminder that shared-config consolidation has hidden blast radius.
• Adds a new shared tsconfig.snaps.json layer, which is one more file in the inheritance chain to reason about.

Clean-install verification

Re-verified from a genuinely fresh worktree — no node_modules, no packages/*/dist anywhere — with only yarn install run (no yarn build):

• yarn lint: passes (exit 0). lint:eslint itself runs build:only-clean first, so it never depended on a prebuilt dist/.
• Raw tsc --noEmit per package (bypassing the root typecheck script's own pre-build step, to test resolution with zero builds anywhere): bitcoin-wallet-snap, sample-snap, snap-networks-utils, solana-wallet-snap, tron-wallet-snap all pass with 0 errors, correctly resolving @metamask/* (including the snap-networks-utils/* subpath) straight from src/ via the node_modules symlink.
• stellar-wallet-snap couldn't run via yarn workspaces foreach ... exec tsc (command not found: tsc) — pre-existing gap: that package's package.json has no typescript devDependency, unrelated to this PR. Running tsc directly against it passes with 0 errors.

Confirms the fix holds in the worst case (fresh clone, install-only, zero builds), not just when a stale dist/ happens to already exist.

References

• Related to feat: layered monorepo readiness (install → types + unit tests) #140
• Compared side-by-side with fix: restate workspace @metamask/* paths per package with local baseUrl #169 (same fix, per-package baseUrl ergonomics) and fix: add TypeScript project references, mirroring MetaMask/core #170 (references-only, does not fix resolution)

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them