chore(lambda): add ADOT Lambda layer v0.48.0 ARNs (CVE remediation)

[priyankaDhingra]

Issue

N/A — Data-only update adding new ADOT Lambda layer ARN versions. No new APIs or behavioral changes.

Reason for this change

ADOT Lambda layers v0.48.0 (OTel Collector v0.151.0, Go 1.26.2) have been released to address 27 CVEs including 2 critical. The CDK fact table and version constants need to be updated so customers using LATEST get the new patched layers.

Description of changes

• fact-tables.ts: Added new ARN entries for all 16 regions × 2 architectures × 5 layer types
• adot-layers.ts: Added new version constants (V1_32_0_2, V1_30_2, V1_32_0, V0_151_0) and updated LATEST pointers
• adot.test.ts + function.test.ts: Updated test expectations to match new LATEST ARNs
• Integration test snapshots: Updated to reflect new LATEST layer versions
• README.md: Updated version note

Description of how you validated changes

• Unit test expectations updated to match new ARNs
• Integration test snapshots regenerated
• Pattern matches previous ADOT layer update PRs (feat(lambda): latest versions for ADOT Lambda Layers (v0.115.0) #32783, chore(cdk): update ADOT Lambda Layer ARNs  #27849, chore: Update arns of ADOT lambda layers #24573)

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES
• Is this fix associated with a breaking change? No
• Does this PR introduce a feature flag? No

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[github-actions]

👋 It looks like your PR description references an issue, but not in the expected location.

The issue number must appear in the first section of the description (the first two lines), following the template format:

### Issue # (if applicable)

Closes #123.

Please move your issue reference to the top of the description.

[aws-cdk-automation]

(This review is outdated)

[priyankaDhingra]

Exemption Request

This PR is a data-only update adding new ADOT Lambda layer ARN versions to the existing fact table and updating LATEST version constants. It does not introduce new APIs, features, or behavioral changes.

Why README change is not applicable: No new constructs, properties, or APIs are added. The existing ADOT layer documentation in the README already describes how to use these layers — only the version numbers changed internally. The user-facing API (AdotLambdaLayerJavaSdkVersion.LATEST) is unchanged.

Why integration test snapshot is included: The integration test snapshots ARE included in this PR (files under integ.lambda-adot.js.snapshot/). The snapshots were updated to reflect the new LATEST ARNs. The integration test source file (integ.lambda-adot.ts) does not need changes because it uses LATEST which automatically resolves to the new versions.

Previous similar PRs: #32783, #27849, #24573 — all follow the same pattern of updating fact tables + adot-layers.ts + test expectations + snapshots.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[priyankaDhingra]

Hi @aws/aws-cdk-maintainers / @aws/aws-cdk-owners can someone help reveiw/merge this PR.