chore(deps): clean up security lockfiles

[TheRealAgentK]

Summary

• update the root lockfile to patched brace-expansion 5.0.7 and 2.1.2 releases
• regenerate both example lockfiles without snapshotting the linked root package's development dependency tree
• remove stale vulnerable transitive entries reported by Dependabot from the example lockfiles

The example applications use raygun through file:../... Their lockfiles had captured the root project's node_modules tree as thousands of ../../node_modules/... development entries. Those entries were neither installed as example runtime dependencies nor representative of the current root lockfile, but GitHub correctly continued to alert on their stale versions.

Validation

• npm ci
• npm test — 258/258 passing
• npm run test:cjs
• npm run eslint
• npm run tseslint
• npx prettier --check 'lib/*.ts' 'test/*.js' 'examples'
• root npm audit — 0 vulnerabilities
• clean npm ci, full npm audit, and npm audit --omit=dev in both examples — 0 vulnerabilities
• Express live checks: /, /skip, /send, and expected /error 500 behavior
• using-domains live check: intentional domain error/catch/send/exit path