chore(deps): clear Gatsby 2 transitive npm deprecation warnings

[jimmyandrade]

Summary

Most remaining install deprecations come from the Gatsby 2 / webpack 4 stack (gatsby@2.32.13 and plugins), not from app source. Examples:

• urix / resolve-url (webpack4 → micromatch → snapdragon → source-map-resolve)
• eslint-loader@2.2.1
• @hapi/joi@15 and related @hapi/* (gatsby + workbox via gatsby-plugin-offline)
• chokidar@2.1.8 (webpack-dev-server@3)
• old rimraf / glob@7 / core-js@2 / debug@4.1.1 / uuid@3 under Gatsby tooling
• older npmlog via sharp under gatsby-plugin-manifest

Leaf-level overrides will not sustainably clear this set.

Parent inventory: #445 (Cluster B).

Recommended paths (in order of preference)

1. Long-term: complete Migrate site from Gatsby to Next.js (App Router) #415 (Gatsby → Next.js) — removes the entire cluster.
2. Medium-term: coordinated Gatsby major upgrade (see open/blocked PRs fix(deps): update dependency gatsby to v4 [security] #421, fix(deps): update dependency gatsby-plugin-sharp to v4 [security] #413, chore(deps): bump socket.io, gatsby, gatsby-plugin-canonical-urls, gatsby-plugin-manifest, gatsby-plugin-offline, gatsby-plugin-react-helmet, gatsby-plugin-sitemap, gatsby-source-filesystem and gatsby-transformer-sharp #432, chore(deps): bump gatsby from 2.32.13 to 4.25.7 #444) with matching plugin majors.
3. Avoid: one-off overrides for every deprecated leaf package.

Acceptance criteria

• Choose path 1 or 2 and link the implementing PR(s)
• After landing, Cluster B warnings from chore(deps): clear npm install deprecation warnings #445 are gone on a clean install
• Build/test CI remains green on Node 18

Related

• Migrate site from Gatsby to Next.js (App Router) #415 Migrate site from Gatsby to Next.js
• chore(deps): remove unused gatsby-image dependency #446 Remove unused gatsby-image (quick win, independent)
• chore(deps): clear npm install deprecation warnings #445 Inventory of npm deprecation warnings