fix: address dependency vulnerabilities and preserve Lambda payloads

[TheRealAgentK]

Summary

Resolve current development-dependency advisories and improve regression and sample integration coverage without changing report payloads or runtime behavior.

• Patch all six vulnerable development dependencies, including ip-address 10.7.3.
• Preserve full Lambda context capture in error custom data and automatic breadcrumbs. Identity, clientContext, application-added fields, and handler mutations remain included as before.
• Document existing capture boundaries and optional onBeforeSend redaction. No automatic filtering, allowlist, or context snapshot is introduced.
• Add payload-compatibility tests for async and callback handlers and deterministic overlap tests: invocation B finishes while A is suspended, with distinct full context and breadcrumbs in each received report.
• Replace the sample smoke check with actual success and error reporting against a localhost mock endpoint, checking preserved context fields and confirming events are not automatically captured.

Verification

• Confirmed lib/raygun.aws.ts is identical to the default-branch implementation: this PR has no runtime-source changes.
• Builds, full handler tests (51 assertions), and sample integration tests (10 assertions) passed locally on Node 20, 22, and 24 after the revision.
• ESLint, TypeScript ESLint, formatting, and git diff checks passed.
• Full and production dependency audits are clean. Registry signatures were verified during the dependency update; this revision does not change the lockfile.
• Sample tests do not contact AWS or live Raygun services.

Compatibility and delivery

The earlier context allowlist proposal has been removed. Existing Lambda report payloads are preserved, including identity, clientContext, application-added fields, and context changes made by handlers. Redaction remains an explicit application choice through the existing Raygun client hook.

Companion Node SDK PR: MindscapeHQ/raygun4node#563

This PR retains the existing published raygun dependency baseline. To deliver the companion Node SDK logging fixes to Lambda users, publish the Node SDK first, then raise this wrapper baseline to that release, refresh its lockfile, and rerun tests against the published package. No version bump or npm publication is included here.

The development-dependency Dependabot alert should close after merging and rescanning the default branch.