chore(deps-dev): align TypeScript 6

[TheRealAgentK]

Summary

• align the Lambda provider with Raygun4Node on TypeScript 6.0.3
• explicitly retain ES5 output with ignoreDeprecations: "6.0"
• set rootDir: "./lib" so the package entry-point layout is explicit ahead of future compiler migrations

This deliberately does not adopt TypeScript 7. TypeScript 7 removes ES5 output and requires a separate runtime/output compatibility decision tracked as future work.

Compatibility

The JavaScript and declaration artifacts emitted by TypeScript 6.0.3 were byte-for-byte compared with the TypeScript 5.9.3 build and are unchanged. A dry-run package confirms the expected entry points remain:

• build/raygun.aws.js
• build/raygun.aws.d.ts

Validation

• npm ci --ignore-scripts
• npm run prepare
• TypeScript 5.9.3 versus 6.0.3 artifact comparison — no diff
• npm test — 13 passing
• npm run eslint
• npm run tseslint
• npm run prettier:check
• npm audit --omit=dev — 0 vulnerabilities
• npm audit — 0 vulnerabilities
• npm pack --dry-run — expected JS and declaration entry points included

[TheRealAgentK]

The approved merge was applied to main, but GitHub returned a server error before updating this PR's state. The change is present on main as commit bce78164b3d3e1d711007a0ded3d47157d7e338b (chore(deps-dev): align TypeScript 6 (#185)) and merge commit 263e863f8f29c8642f54bf0e09535c23771abfe3.

The PR head is now an ancestor of main, and git diff origin/main origin/chore/align-typescript-6 is empty. GitHub therefore reports the still-open PR as non-mergeable even though its complete contents have landed. Closing the stale PR record to reflect the effective merge; no changes are being discarded.