chore: Release 0.0.10

[TheRealAgentK]

Summary

Prepare @raygun.io/aws-lambda 0.0.10 following the published Raygun Node SDK 2.2.10 release.

• Bump the provider version to 0.0.10 and synchronize root and example lockfiles.
• Raise the raygun runtime dependency baseline to ^2.2.10 and lock the published registry package at 2.2.10.
• Finalize release notes for the dependency fixes, context-preservation regression coverage, example integration, and opt-in redaction documentation merged in fix: address dependency vulnerabilities and preserve Lambda payloads #201.
• Lambda runtime source is unchanged. Full context capture, handler behavior, report payloads, and public APIs remain unchanged. The updated Node SDK removes sensitive content from diagnostic logs, not from reports sent to Raygun.

Verification

• Clean root and example installs passed using the published raygun@2.2.10 package, not a local SDK checkout.
• Build, tests, example success/error reporting against a local endpoint, and JavaScript/TypeScript lint passed on Node 20.20.2, 22.19.0, and 24.21.0.
• Formatting passed.
• Full dependency audit reported zero vulnerabilities; all 452 root dependencies have verified registry signatures.
• npm publish --dry-run passed with compiled JavaScript and TypeScript declarations included.
• Confirmed no lib/ changes against main.

Release status

This provider has not been published or tagged. Following RELEASING.md, approve the PR before publishing @raygun.io/aws-lambda@0.0.10, then merge into main and create the release tag/GitHub release. Publishing remains a separate action.

[QuantumNightmare]

👍